Hi everybody.
I found the following bug while running some of my bash scripts on
GNU/Linux with stdout redirected to /dev/full, to see if write errors
where correctly detected and reported.
It turned out that, on write errors, the printf builtin correctly
returns a non-zero status (thus my
Can someone explain this to me? Why am I not seeing correct results from
ulimit after ssh into localhost? Thanks!
$ ssh localhost bash -c 'ulimit -a'
unlimited
but
$ bash -c 'ulimit -a'
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority
peter360 wrote:
Can someone explain this to me? Why am I not seeing correct results from
ulimit after ssh into localhost? Thanks!
$ ssh localhost bash -c 'ulimit -a'
unlimited
You have insufficiently quoted your argument to ssh. This is causing
bash not to get ulimit -a but to get ulimit
Bob,
Thanks for the quick reply! A local unix guru also told me the same thing.
So, just to make sure I really understand this, here is how I understand ssh
worked: even thought I gave the command bash -c 'ulimit -a' as 3 separate
strings, ssh (either the client or the server) actually
peter360 wrote:
So, just to make sure I really understand this, here is how I understand ssh
worked: even thought I gave the command bash -c 'ulimit -a' as 3 separate
strings,
Yes.
ssh (either the client or the server) actually concatenate them into
one,
No. It isn't put into one string
Stefano Lattarini wrote:
Hi everybody.
I found the following bug while running some of my bash scripts on
GNU/Linux with stdout redirected to /dev/full, to see if write errors
where correctly detected and reported.
It turned out that, on write errors, the printf builtin correctly
Tried adding each of -lcurses and -lncurses with the following results:
/home/users/tovrea/local/sgi6/bin/gcc -L./builtins -L./lib/readline
-L./lib/readline -L./lib/glob -L./lib/tilde -L./lib/sh
-L/home/users/tovrea/local/sgi6/lib/gcc/mips-sgi-irix6.5/4.3.0
