On Fri, 2015-06-05 at 20:50 +0200, SkyFish wrote:
> Thank you for the prompt reply! Unfortunatelly, I can't open a local
> console, the box has VGA output and I have no VGA monitor.
Buy an adapter! ;)
> So, SSH is
> the only option. But I do can boot a clean SQUEEZE system, mount the
> root f
Thank you for the prompt reply! Unfortunatelly, I can't open a local
console, the box has VGA output and I have no VGA monitor. So, SSH is
the only option. But I do can boot a clean SQUEEZE system, mount the
root file system of the broken JESSIE system and download log files.
What information s
t; funktion without any problems. The last two, wheezy and jessie, start
> without problems, and also let me to connect over SSH. But after 1-2
> minutes the client terminal freezes and the outputs this error message:
> "packet_write_wait: Connection to 192.168.1.2: Broken pipe".
thout problems, and also let me to connect over SSH. But after 1-2
minutes the client terminal freezes and the outputs this error message:
"packet_write_wait: Connection to 192.168.1.2: Broken pipe". The network
activity LED on the box is flushing permanently. After that, no more
connectio
On Tue, Jul 01, 2014 at 03:08:54AM +0200, Tamer Higazi wrote:
> Hi people!
> I really don't know, how to solve this problem. Does any of you have an
> idea ?!
>
>
>
> root@babe3306:/home/tamer# apt-get install -f
> Preparing to unpack .../libsope1_2.2.5-1_amd64.deb ...
> Unpacking libsope1 (2.2.
ack):
> trying to overwrite '/usr/lib/libDOM.so.4.9.24', which is also in
> package libsope-xml4.9 4.9.r1664.20140307
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
> /var/cache/apt/archives/libsope1_2.2
write '/usr/lib/libDOM.so.4.9.24', which is also in
package libsope-xml4.9 4.9.r1664.20140307
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libsope1_2.2.5-1_amd64.deb
E: Sub-process /usr/bin/dpkg re
ike
cp large_file4gb large_copy4gb
that even though the command produces no output you then get broken
pipe? If so the connection is likely being terminated because it's idle
(check your internet provider). The keepalive should prevent this.
If you log in and do a
ls -R /
do you get the o
Karl E. Jorgensen wrote:
> I've seen that before and it took us ages to narrow down - in our case
> (admittedly your case may be different), it was the combination of
> network interface MTU and packet fragmentation.
I was just going to suggest exactly the same thing. And it took us ages
to track
gt; > every 5 seconds to keep it alive.
> >
> > To summarise, I get rid of broken pipe errors by using this command line
> >
> > ssh -o ServerAliveInterval=5 u...@server.com
> >
> > Hope this helps,
> > elbbit
> I can try it, but as I said, I have a stabl
of data on the remote server, I get
> kicked out of my ssh session with a "Write failed: Broken pipe" error.
I've seen that before and it took us ages to narrow down - in our case
(admittedly your case may be different), it was the combination of
network interface MTU and packet fra
ing that if you log in by SSH then issue a command like
cp large_file4gb large_copy4gb
that even though the command produces no output you then get broken
pipe? If so the connection is likely being terminated because it's idle
(check your internet provider). The keepalive should preven
. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do "-o ServerAliveInterval=5" which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command li
too little back-and-forth
traffic. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do "-o ServerAliveInterval=5" which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe
e is too little back-and-forth
>> traffic. My ISP is a mobile phone network over 3G so they are probably
>> trying to keep the bandwidth for phones only.
>>
>> I do "-o ServerAliveInterval=5" which has my ssh client ping the server
>> every 5 seconds to keep
3G so they are probably
trying to keep the bandwidth for phones only.
I do "-o ServerAliveInterval=5" which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o ServerAliveInterval=5 u...@
to keep the bandwidth for phones only.
I do "-o ServerAliveInterval=5" which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o ServerAliveInterval=5 u...@server.com
Hope this helps,
e
I'm connecting at various times to different Debian/Squeeze servers from
my Debian/Wheezy workstation using ssh. No matter which server I connect
to, I find that if I move a lot of data on the remote server, I get
kicked out of my ssh session with a "Write failed: Broken pipe"
Kevin B. McCarty wrote:
Hi Scott,
Scott wrote:
But seriously folks...
What's a "broken pipe"?
A pipe is this keyboard symbol: |
That part I knew. :-)
When you want to use the output of one command as the input of another
command, you "pipe" it, like this: ls
Hi Scott,
Scott wrote:
> But seriously folks...
>
> What's a "broken pipe"?
A pipe is this keyboard symbol: |
When you want to use the output of one command as the input of another
command, you "pipe" it, like this: ls -l | sort
A broken pipe happens w
I have sarge running with the dcc-client and spamd running. I have been
getting the following messages in my syslog - they appear after spamd
completes processing the message:
Dec 2 07:20:30 debian dccifd[5800]: write(MTA socket,88): Broken pipe
Note that this does not appear after every
On Mon, Nov 28, 2005 at 05:32:09PM +0800, Marcus Deluigi (intern) wrote:
>
> Hi!
>
> I tried to install an unofficial debian package (AMPortal) by adding a
> new ressource to resources.list.
> But the installation failed with the error message:
[...]
The problem is that your unofficial package
> (intern) wrote:
> > trying to overwrite `/usr/share/asterisk/sounds/ext-or-zero.gsm',
> > which is also in package asterisk
>
> ^^^ the package conflicts with `asterisk'.
>
> > and I can't install any other packages anymore, because apt-get
> > reports unmet dependencies:
> >
> > ---
> > Th
On Mon, Nov 28, 2005 at 05:32:09PM +0800, Marcus Deluigi (intern) wrote:
> trying to overwrite `/usr/share/asterisk/sounds/ext-or-zero.gsm', which
> is also in package asterisk
^^^ the package conflicts with `asterisk'.
> and I can't install any other packages anymore, because apt-get reports
>
', which
is also in package asterisk
-sounds-extra
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/asterisk-sounds-amportal_1.10.009-42_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
and I can't i
On Wed, 09 Nov 2005 17:52:21 -0500
"H.S." <[EMAIL PROTECTED]> wrote:
> H.S. wrote:
> > Hi,
> >
> > I am having trouble since looong to make xmms play m3u playlist
> > files. Here is the problem:
> > If I click on an m3u link on a webpage in mozilla, xmms starts but
> > gives an error: "Couldn't c
I download the m3u file (listen.m3u) from the website and tried
> starting xmms from command line and got this error (and the dialog box
> saying couldn't connect to host):
> #--
> $> xmms listen.m3u
> Message: dev
$> xmms listen.m3u
Message: device: default
** WARNING **: ctrl_write_packet(): Failed to send data: Broken pipe
#--
Next, I played the file with mplayer and it worked perfectly:
#--
$> mplayer -playlist listen.m3u
on
process killed by signal (Broken Pipe)
Any Ideas how to work around?
--
Regards, Dave
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libdb.so.3: cannot open
>> shared object file: No such file or directory
>> E: Write error - write (32 Broken pipe)
>> E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
>> sid:~#
>>
>>
>> Nevere ran into an error of this type. Should have I upgr
ved.
> > Need to get 0B/19.5MB of archives. After unpacking 13.0MB will be
> used.
> > Do you want to continue? [Y/n]
> > perl: error while loading shared libraries: libdb.so.3: cannot
> open
> > shared object file: No such file or directory
> > E: Write error
d libraries: libdb.so.3: cannot open
> shared object file: No such file or directory
> E: Write error - write (32 Broken pipe)
> E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
> sid:~#
>
>
> Nevere ran into an error of this type. Should have I upgraded to woo
d libraries: libdb.so.3: cannot open
> shared object file: No such file or directory
> E: Write error - write (32 Broken pipe)
> E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
> sid:~#
>
>
It is not finding some perl modules that it needs. The required packages
Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
sid:~#
Nevere ran into an error of this type. Should have I upgraded to woody
first, then unstable? Any suggestions appreciated.
--- [EMAIL PROTECTED] wrote:
> In attempting to dpkg -i libgtk1.2_1.2.6-1.deb, the current potato
> libgtk, I'm getting the following:
>
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> dpkg: error processing libgtk1.2_1.2.6-1.deb) ...
> subprocess dpkg-deb
In attempting to dpkg -i libgtk1.2_1.2.6-1.deb, the current potato
libgtk, I'm getting the following:
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing libgtk1.2_1.2.6-1.deb) ...
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Could someone p
e from cron:
>
> /etc/cron.daily/popularity-contest:
> /usr/bin/dpkg-awk: line 31: 2988 Broken pipe mawk $incf -f
> +/usr/lib/awk/dpkg-awk.lib -- "--exebase=`basename $0`" "--exedir=`dirname
> $0`"
> +"$@"
I installed popularity-contest (stable) on my machine and every day I get
the following message from cron:
/etc/cron.daily/popularity-contest:
/usr/bin/dpkg-awk: line 31: 2988 Broken pipe mawk $incf -f
+/usr/lib/awk/dpkg-awk.lib -- "--exebase=`basename $0`" "--exe
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
> ** Reply to note from Art Lemasters <[EMAIL PROTECTED]> Mon, 23 Mar 1998
> 00:20:29 -0600 (CST)
> >
> > default, or my bo was broken. In any case, less was an excellent idea
> > for a default for manpage paging.
>
> Quite honestly I can'
On Mon, Mar 23, 1998 at 09:38:53AM -0600, [EMAIL PROTECTED] wrote:
> On Mon, 23 Mar 1998, Bill Leach wrote:
>
> : I think that it is mostly historical (just about every Unix system since
> : about 1970 has had 'more').
> :
> : There are some other reasons that are now at least mostly not
> : appl
On Mon, 23 Mar 1998, Bob Hilliard wrote:
: On Mon, 23 Mar 1998 09:27:21 -0600 (CST) <[EMAIL PROTECTED]> wrote:
: > One thing it will change is the behavior of 'make config' when
: > recompiling the kernel ... namely when you choose ``?'' to get more
: > information about that particular option. `
On Mon, 23 Mar 1998 09:27:21 -0600 (CST) <[EMAIL PROTECTED]> wrote:
> One thing it will change is the behavior of 'make config' when
> recompiling the kernel ... namely when you choose ``?'' to get more
> information about that particular option. ``less'' will make you choose
> ``q'' to get back t
On Mon, 23 Mar 1998, Bill Leach wrote:
: I think that it is mostly historical (just about every Unix system since
: about 1970 has had 'more').
:
: There are some other reasons that are now at least mostly not
: applicable. For example, 'more' will work on a printing terminal but I
: believe tha
On Mon, 23 Mar 1998, E.L. Meijer (Eric) wrote:
[ snipped discussion of less vs. more ]
: Excellent comment, now let's go all the way and tell them newbie people
: how to _do_ it :)
:
: in bask/ksh: export PAGER less
: in csh/tcsh: setenv PAGER less
Excellent support :) BTW, these lines could b
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
[ snip ]
: (one newbie user who is looking forward to a new stable debian release that
: hopely won't include such obvious archiac software)
Hmm ... well, I hope it includes new _and_ "archaic" software ... some
of that stuff's quite useful! ;)
(a
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
> > Some wonderful developer(s) fixed our manpage readers of
> > the coming release (hamm) so that they will also scroll upwards
> > to the beginning of any file we read. The manpages (accessed
> > by typing "man nameofcommand"--without the quo
I think that it is mostly historical (just about every Unix system since
about 1970 has had 'more').
There are some other reasons that are now at least mostly not
applicable. For example, 'more' will work on a printing terminal but I
believe that 'less' will not. There might be other VDTs that c
Marcelo E. Magallón <[EMAIL PROTECTED]> writes:
> [79 jacinta:~] while true ; do echo -n . ; /usr/sbin/update-alternatives
> --display WindowMaker | grep -q 'WindowMaker-newstyle' ; done
> .Broken pipe
>From the grep man page:
-q, --quiet
Q
hamish wrote:
>
> On Mon, Mar 23, 1998 at 10:37:39AM +0100, E.L. Meijer (Eric) wrote:
> > in bask/ksh: export PAGER less
>
> You want
>
> export PAGER=less
>
> I do believe.
>
Yep, moreover, I meant `bash' and not `bask'. Maybe Monday mornings
aren't the right time for emailing to the debia
On Mon, Mar 23, 1998 at 10:37:39AM +0100, E.L. Meijer (Eric) wrote:
> in bask/ksh: export PAGER less
You want
export PAGER=less
I do believe.
hamish (a tcsh user)
--
Hamish Moffatt Mobile: +61 412 011 176 [EMAIL PROTECTED]
Rising Software Australia Pty. Ltd.
Developers of music
>
> On Sun, 22 Mar 1998, Art Lemasters wrote:
>
> > Some wonderful developer(s) fixed our manpage readers of
> > the coming release (hamm) so that they will also scroll upwards
> > to the beginning of any file we read. The manpages (accessed
> > by typing "man nameofcommand"--without the qu
** Reply to note from Art Lemasters <[EMAIL PROTECTED]> Mon, 23 Mar 1998
00:20:29 -0600 (CST)
>
> default, or my bo was broken. In any case, less was an excellent idea
> for a default for manpage paging.
Quite honestly I can't think of any DOS, Windows or OS/2 text file viewer
prog
Addressed to: Art Lemasters <[EMAIL PROTECTED]>
Debian
** Reply to note from Art Lemasters <[EMAIL PROTECTED]> Sun, 22 Mar 1998
23:41:26 -0600 (CST)
>
>
> Some wonderful developer(s) fixed our manpage readers of
> the coming release (hamm) so that they will also sc
Adam wrote the enlightenment:
> On Sun, 22 Mar 1998, Art Lemasters wrote:
>
> > Some wonderful developer(s) fixed our manpage readers of
> > the coming release (hamm) so that they will also scroll upwards
> > to the beginning of any file we read. The manpages (accessed
> > by typing "man nam
On Sun, 22 Mar 1998, Art Lemasters wrote:
> Some wonderful developer(s) fixed our manpage readers of
> the coming release (hamm) so that they will also scroll upwards
> to the beginning of any file we read. The manpages (accessed
> by typing "man nameofcommand"--without the quotes) can also
good work! Soon, Debian LINUX will be everywhere.
Art
Shaleh enlightened:
> "Broken pipe" means that the '|" did not recieve any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"Broken pipe" means that the '|" did not recieve any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I get this:
[79 jacinta:~] while true ; do echo -n . ; /usr/sbin/update-alternatives
--display WindowMaker | grep -q 'WindowMaker-newstyle' ; done
.....Broken pipe
..Broken pipe
..Broken pipe
...Broken pipe
..^C
do you see a problem with the statement? (It's just for test pur
with no sound card, and it didn't crash.
The old a.out Doom always crashed for me without sound cards. Usually
nothing so clean as a broken pipe either; it would leave the keyboard
in some weird mode, as well as the console. Not too easy to fix without
rebooting.
Hamish
--
Hamish Moffatt,
Þann 01-Jan-98 skrifar Joey Hess:
>
> You can edit your ~/.doomrc, and there is a line in there that lets you
> configure the path to the sndserver.
>
yeah, I took a peak at the source and found the M_LoadDefaults routine, and
some of the keywords. The 'key_fire' is especially interresting, s
Orn E. Hansen wrote:
> The problem was, that I am using NAS to network'ize my soundcard, and that
> meant doom couldn't acquire the card. Whenever I move the cursor in the menu,
> there is a sound, which is why it broke.
>
> There is a sndserver for NAS, and I compiled it. It seems to work o
Þann 01-Jan-98 skrifar Joey Hess:
>
> What version of doom are you using? Do you have doom-musserver installed,
> and if so, what version? Do you have a sound card?
>
The problem was, that I am using NAS to network'ize my soundcard, and that
meant doom couldn't acquire the card. Whenever I m
Orn E. Hansen wrote:
> Has anyone gotten DOOM to work? Here, the program starts, but when I try to
> move the cursor, or press any ke, after the Menu comes up the program stops
> with the message 'broken pipe'. Any ideas?
What version of doom are you using? Do you
Has anyone gotten DOOM to work? Here, the program starts, but when I try to
move the cursor, or press any ke, after the Menu comes up the program stops
with the message 'broken pipe'. Any ideas?
Orn Ei
When I try to get dselect to recognize the CD as a file source, I have to
enterthe distribution top level. Whatever reasonable response I give, it breaks:
/usr/lib/dpkg/methods/disk/setup: line 8: 343 Broken pipe [...]
I don't know what adverse effect this is having (if any), but
On Mon, 9 Jun 1997, Rick Macdonald wrote:
> On Mon, 9 Jun 1997, Tim O'Brien wrote:
> > Ok, I finally have to break down and ask a potential dumb question: What
> > the heck is a 'broken pipe'? I get these from time to time on my Debian box.
>
> A pipe is when t
On Mon, 09 Jun 1997 22:49:22 CDT "Tim O'Brien" ([EMAIL PROTECTED]
) wrote:
> Ok, I finally have to break down and ask a potential dumb question: What
> the heck is a 'broken pipe'? I get these from time to time on my Debian box.
Err, first what is a pipe ?
A pipe
On Mon, 9 Jun 1997, Tim O'Brien wrote:
> Ok, I finally have to break down and ask a potential dumb question: What
> the heck is a 'broken pipe'? I get these from time to time on my Debian box.
A pipe is when the standard output of one program is fed to the standard
input of
I think it is a problem of bash package. I downgrade to 1.14 from
debian 1.2 and no more broken pipe.
Last time, tetex warned that my system was in a inconsistent state and I
suspected it is casued by the broken pipe.
Lawrence,
Tim O'Brien wrote:
>
> Ok, I finally have to break dow
Ok, I finally have to break down and ask a potential dumb question: What
the heck is a 'broken pipe'? I get these from time to time on my Debian box.
Thanks,
Tim
-
LINUX 2.0.6 i486 Because reboots are fo
70 matches
Mail list logo
