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
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
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
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
William L. Maltby wrote:
On Mon, 2008-03-24 at 16:19 -0500, Dan Bongert wrote:
mouss wrote:
Dan Bongert wrote:
Hello all:
snip
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
be publicly accessible; it's behind
our firewall.
Thanks.
--
Dan Bongert [EMAIL PROTECTED]
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
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
7 matches
Mail list logo
