Yap, Bill.
The backslash-escaping one works for my zsh as well. And I'm sure you
checked it's working for other major shells.
So I would say backslash seems to be a good solution since you don't have to
worry about double-single quotes.
Thanks!
regards,
-Hui
On 11/1/06, Bill Au [EMAIL
It looks like find running under zsh is the problem. In this case it does
like the wildcard (*).
I don't really know zsh so I will have to spend some time to investigate.
Bill
On 10/30/06, Yu-Hui Jin [EMAIL PROTECTED] wrote:
Hi, Hoss,
Thanks for the reply!
For #2, I think I just need to
On 10/31/06, Chris Hostetter [EMAIL PROTECTED] wrote:
Bill: what do you think about explicitly putting in the single quotes as
Hui suggested? that should still work under bash and sh right?
That should work in bash, at least. Backslash-escaping is also an option.
The semantics of file
: Here's a problem I got. It says there's no match for snapshot.* found on the
: master box. This is wrong, there's one such file exists.
:
: - I then ran snappuller specifically on the snap file that's on the master:
: ./bin/snappuller -n snapshot.20061023172655
:
: This time it worked. and
Hi, Hoss,
Thanks for the reply!
For #2, I think I just need to setup the passwordless SSH with empty
passphase. right?
For #1:
I'm using the following Enterprise version:
Linux version 2.4.21-37a6 (gcc version 3.2.3 20030502 (Red Hat Linux
3.2.3-47))
I tried to run the find command
find
