search for: redirecton

...ecisely the reason that ssh couldn't ever do the > > Yes, exactly. > > But for? > ssh remhost ls -l \>foo > > ? it MUST NOT quote the I/O redirection sign, otherwise > the redirection would not work. That?s why I?m saying it > needs not and must not quote. The redirecton sign isn't a space. We're talking about spaces. But the redirection does have to "quoted" locally otherwise it would apply to the local process, but it would need to be quoted like this: ssh remhost "ls -l >foo" > bye, > //mirabilos (current developer of a P...

On Sat, 27 May 2023, raf wrote: >So, perhaps this could be added to the existing >sentence/paragraph: > > "so any spaces in individual arguments must be Must they? No, a single space will do just fine. > quoted using the syntax of the destination > user's login shell". ? keeping in mind the source shell?s quoting as well. >If an example were needed,

Hi, I would like to log whatever happens with rsync on client side when it runs with Cygwin on NT4. First, I just did a redirect of the screen output to a log-file: rsync -rtv --delete --modify-window=2 --stats /cygdrive/g/users/bco/test/ bee2bs01::d/test/ >>c:\rsync\log\%FDATE%.log The problem with this method is that it does not redirect whatever Rsync reports as errors; because they

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Shorewall-3.0.3 RH9 (+legacy updates) eth0: loc: 192.168.1.0/24 eth0:0: loc: 192.168.20.0/24 eth1:: 69.70.32.8/29 I''m worked all day on an issue I found today and I just can''t find a way to fix my problem. So, basically, for now, my network looks like this: Internet ^ | (69.70.32.8/29) Firewall 192.168.1.1