imited
> open files (-n) 1024
> pipe size(512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 8185
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> However I think it is simpler to avoid the argument processing and
> instead using stdin to the shell.
>
> $ echo ulimit -a | ssh localhost bash
>
> Isn't that simpler?
>
> Bob
>
>
>
>
--
View this message in context:
http://old.nabble.com/ulimit-and-ssh--tp25262471p27086055.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
peter360 wrote:
> Thanks Adreas. That was what I suspected in my reply to Bob. But Bob
> disagreed. Looks like there were some confusion about this feature even
> among experts. Seems another reason to deprecate the feature.
I don't think anything I said disagreed with what Andreas said. It
ny quoting in this process you need to quote them.
>
> Andreas.
>
> --
> Andreas Schwab, sch...@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
>
>
>
--
View this m
peter360 writes:
> That makes sense. So the "feature" is to split all parameters on space even
> if they are quoted?
The feature is that ssh concatenates all remaining arguments to a single
string and passes that to the shell on the remote side. If you want to
preserve any quoting in this proc
peter360 writes:
> In my case, I just got
>
> $ ssh localhost bash -x -c 'ulimit -a'
> unlimited
> + ulimit
Try ssh -v as Marc wrote.
debug1: Sending command: bash -x -c ulimit -a
The quotes are lost at this point.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA
Enabling tracing options usually helps a lot.
>
>
> Instead of this:
> sshlocalhost bash-c 'ulimit -a'
>
> Try this:
> ssh -v localhost bash -x -c 'ulimit -a'
>
>
> (And as usual, check out the "Guide to unix shell quoting")
>
>
>
>
--
View this message in context:
http://www.nabble.com/ulimit-and-ssh--tp25262471p25530174.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
localhost $HOME/bin/args 'ulimit -a'
> 2 args: 'ulimit' '-a'
> imadev:~$ ssh localhost $HOME/bin/args 'ulimit -a'
> wool...@localhost's password:
> 2 args: 'ulimit' '-a'
>
>
>
>
--
View this message in context:
http://www.nabble.com/ulimit-and-ssh--tp25262471p25530173.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
peter360 a écrit :
> Thanks for the explanation. So my understanding of the way ssh works is
> still incorrect. I am confused about at which point the two parameters,
> "-c" and "ulimit -a" were converted into three, "-c", "ulimit", and "-a". I
> guess I need to read the source of ssh and bas
On Tue, Sep 08, 2009 at 11:39:02AM -0700, peter360 wrote:
> Thanks for the explanation. So my understanding of the way ssh works is
> still incorrect. I am confused about at which point the two parameters,
> "-c" and "ulimit -a" were converted into three, "-c", "ulimit", and "-a". I
> guess I n
t;> strings,
>
> Yes.
>
>> ssh (either the client or the server) actually concatenate them into
>> one,
>
> No. It isn't put into one string unless you quote it as one string.
>
>
--
View this message in context:
http://www.nabble.com/ulimit-and-ssh--tp25262471p25351813.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
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 stri
to get "ulimit" "-a" instead. You are
> seeing the output of "ulimit".
>
> Try this:
>
> ssh localhost "bash -c 'ulimit -a'"
>
> And this:
>
> echo ulimit -a | ssh localhost bash
>
> Bob
>
>
>
>
--
View this message in context:
http://www.nabble.com/ulimit-and-ssh--tp25262471p25263766.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
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
mited
--
View this message in context:
http://www.nabble.com/ulimit-and-ssh--tp25262471p25262471.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
14 matches
Mail list logo