[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: su rc 141
Re: su rc 141
Thu, 14 Feb 2008 21:38:01 -0700
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20071031 Thunderbird/18.104.22.168 Mnenhy/0.7.5.666
-----BEGIN PGP SIGNED MESSAGE-----
According to Marco Salvi on 2/14/2008 5:21 AM:
| I'm on Suse Linux 10 - coreutils-5.93-22.14
Consider upgrading. The latest stable coreutils is at 6.10.
| I moved the base home dir of my user from /home to /local_home.
| Each time I tried to run the su command within a gmd session it exits
| with rc 141.
| The same command works fine in a console. I wasn't able to figure out
| what rc 141 stand for.
Generally, exit statuses greater than 128 imply that the process was
killed abruptly due to a signal. You can use 'kill -l 141' to find out
which signal; many machines use 141 for SIGPIPE. If that is the case,
then it probably means your su session was terminated abruptly because it
writing output to a pipe where the reader had closed. If you are still
having problems, perhaps showing an actual session with what you typed and
what was displayed may allow us to give you better advice, than just
describing the problem in prose.
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
- su rc 141, Marco Salvi, 2008/02/14
- Re: su rc 141,
Eric Blake <=