Dan Bongert wrote:
> Dan Bongert wrote:
> > Filipe Brandenburger wrote:
> >> Hi,
> >>
> >> On Tue, Mar 25, 2008 at 2:21 PM, Dan Bongert <[EMAIL PROTECTED]> wrote:
> >>> thoth(3) /tmp> ls
> >>>
> >>> thoth(4) /tmp> echo $?
> >>> 141
> >>
> >> 141 is SIGPIPE. If the process is killed by a signal,
Dan Bongert wrote:
Filipe Brandenburger wrote:
Hi,
On Tue, Mar 25, 2008 at 2:21 PM, Dan Bongert <[EMAIL PROTECTED]> wrote:
thoth(3) /tmp> ls
thoth(4) /tmp> echo $?
141
141 is SIGPIPE. If the process is killed by a signal, the return code
will be 128+signal number. 141-128=13, and kill -l
Filipe Brandenburger wrote:
Hi,
On Tue, Mar 25, 2008 at 2:21 PM, Dan Bongert <[EMAIL PROTECTED]> wrote:
thoth(3) /tmp> ls
thoth(4) /tmp> echo $?
141
141 is SIGPIPE. If the process is killed by a signal, the return code
will be 128+signal number. 141-128=13, and kill -l says: 13) SIGPIPE.
mouss wrote:
Dan Bongert wrote:
mouss wrote:
Dan Bongert wrote:
Hello all:
I have a couple CentOS 4 servers (all up-to-date) that are having
strange command failures. I first noticed this with a perl script
that uses lots of system calls.
thoth(66) /tmp> uname -a
Linux thoth.ssc.wisc.edu
Kai Schaetzl wrote:
William L. Maltby wrote on Tue, 25 Mar 2008 16:18:51 -0400:
"~>" ? Got me on that one.
home dir plus prompt. It looks funny, yes :-)
Yup, that's exactly it -- I had run that command from my homedir instead of
from /tmp.
--
Dan Bongert [EMAIL PROTEC
William L. Maltby wrote on Tue, 25 Mar 2008 16:18:51 -0400:
> "~>" ? Got me on that one.
home dir plus prompt. It looks funny, yes :-)
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
___
Ce
Hi,
On Tue, Mar 25, 2008 at 2:21 PM, Dan Bongert <[EMAIL PROTECTED]> wrote:
> thoth(3) /tmp> ls
>
> thoth(4) /tmp> echo $?
> 141
141 is SIGPIPE. If the process is killed by a signal, the return code
will be 128+signal number. 141-128=13, and kill -l says: 13) SIGPIPE.
SIGPIPE means that somet
Dan Bongert wrote:
mouss wrote:
Dan Bongert wrote:
Hello all:
I have a couple CentOS 4 servers (all up-to-date) that are having
strange command failures. I first noticed this with a perl script
that uses lots of system calls.
thoth(66) /tmp> uname -a
Linux thoth.ssc.wisc.edu 2.6.9-67.0.7.E
On Tue, 2008-03-25 at 13:21 -0500, Dan Bongert wrote:
> William L. Maltby wrote:
> > On Mon, 2008-03-24 at 16:19 -0500, Dan Bongert wrote:
> >> mouss wrote:
> >>> Dan Bongert wrote:
> Hello all:
>
>
> >
> >
> >> Though 'ls' was just an example -- just about any program will fail.
William L. Maltby wrote:
On Mon, 2008-03-24 at 16:19 -0500, Dan Bongert wrote:
mouss wrote:
Dan Bongert wrote:
Hello all:
Though 'ls' was just an example -- just about any program will fail. The 'w'
command will fail too:
thoth(118) /tmp> w
16:06:51 up 5:34, 1 user, load average:
On Mon, 2008-03-24 at 16:19 -0500, Dan Bongert wrote:
> mouss wrote:
> > Dan Bongert wrote:
> >> Hello all:
> >>
> >>
> Though 'ls' was just an example -- just about any program will fail. The 'w'
> command will fail too:
>
> thoth(118) /tmp> w
>16:06:51 up 5:34, 1 user, load average: 0.9
On Mon, Mar 24, 2008 at 04:18:49PM -0500, Dan Bongert wrote:
>> You can also try running ``strace /bin/ls'' to see what is going on.
> Funnily enough, running strace will work just fine. Though, as I said, just
> about any command will fail -- 'ls' was just for testing purposes.
That's funny. Or
mouss wrote:
Dan Bongert wrote:
Hello all:
I have a couple CentOS 4 servers (all up-to-date) that are having
strange command failures. I first noticed this with a perl script that
uses lots of system calls.
thoth(66) /tmp> uname -a
Linux thoth.ssc.wisc.edu 2.6.9-67.0.7.ELsmp #1 SMP Sat Mar
Bill Campbell wrote:
On Mon, Mar 24, 2008, Dan Bongert wrote:
Hello all:
I have a couple CentOS 4 servers (all up-to-date) that are having strange
command failures. I first noticed this with a perl script that uses lots of
system calls.
Basically, sometimes a command just won't run:
thoth(
Dan Bongert wrote:
Hello all:
I have a couple CentOS 4 servers (all up-to-date) that are having
strange command failures. I first noticed this with a perl script that
uses lots of system calls.
Basically, sometimes a command just won't run:
thoth(52) /tmp> ls
thoth(53) /tmp> ls
thoth(54)
On Mon, Mar 24, 2008, Dan Bongert wrote:
>Hello all:
>
>I have a couple CentOS 4 servers (all up-to-date) that are having strange
>command failures. I first noticed this with a perl script that uses lots of
>system calls.
>
>Basically, sometimes a command just won't run:
>
>thoth(52) /tmp> ls
>
.
16 matches
Mail list logo