From: Alexey Bochenin <bochenin@avtlg.ru>
To: community@lists.altlinux.org
Subject: Re: [Comm] man через ssh
Date: Fri, 25 Feb 2011 11:49:22 +0300
Message-ID: <4D676D12.1020108@avtlg.ru> (raw)
In-Reply-To: <4D668B5C.9070300@avtlg.ru>
24.02.2011 19:46, Alexey Bochenin пишет:
> Кстати, аналогичную ситуацию наблюдается не только в сизифе, но и гноме P5.
> $ ssh localhost -- man -w bash
>
> bzip2: I/O or other error, bailing out. Possible reason follows.
> bzip2: Broken pipe
> Input file = /usr/share/man/ru/man1/bash.1.bz2, output file = (stdout)
> /usr/share/man/ru/man1/bash.1.bz2
> $
>
> Доберусь до 5.1 - проверю и там
В свежеустановленном в виртуалбоксе 5.1 ошибки нет.
По мотивам
http://lists.mindrot.org/pipermail/openssh-unix-dev/2000-December/003484.html,
провел тестирование в виртуальном P5, и broken pipe тут как тут.
[bochenin@host-15 /]$ ssh localhost -- LANG=C yes|head -1
bochenin@localhost's password:
y
yes: standard output: Broken pipe
yes: write error
[bochenin@host-15 /]$
На рабочем компьютере тоже наблюдаю ошибку.
Но после рестарта sshd все исправилось в том числе и проблемы с man
через ssh.
Итог: причина осталась для меня непонятной, рестарт sshd исправляет
ситуацию с broken pipe.
--
WBR, Alexey
next prev parent reply other threads:[~2011-02-25 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 6:07 Alexey Bochenin
2011-02-24 9:28 ` Dmitry Chistikov
2011-02-24 10:57 ` Alexey Bochenin
2011-02-24 12:55 ` Dmitry Chistikov
2011-02-24 16:46 ` Alexey Bochenin
2011-02-24 18:28 ` Dmitry Chistikov
2011-02-24 19:08 ` Dmitry Chistikov
2011-02-25 8:49 ` Alexey Bochenin [this message]
2011-03-03 9:45 ` Dmitry Chistikov
2011-03-03 10:59 ` Alexey Bochenin
2011-03-03 11:32 ` Dmitry Chistikov
2011-03-04 12:11 ` Alexey Bochenin
2011-03-05 7:40 ` Dmitry Chistikov
2011-03-28 10:58 ` Dmitry Chistikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D676D12.1020108@avtlg.ru \
--to=bochenin@avtlg.ru \
--cc=community@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git