|
Title: s3sync --some_options >/path/to/log.log works *after* quitting s3sync Post by: maelcum on April 23, 2007, 10:36:54 AM hokay... difficult to explain, so please bear with me...
when I call something like "s3sync.rb -v -r -s /volume/dir hostname: >/volume/dir/file.log" s3sync works beautifully, though nothing shows up in the log while it is running. Once I quit s3sync, the log is filled. Calling the line without the ">/volume/dir/file.log" at the end (to redirect output) gives me the single lines of s3sync operations. This might be related to my machine, my os (linux 2.4.something) or my mistake. I just wonder if I'm doing anything wrong. Thanks. maelcum Title: Re: s3sync --some_options >/path/to/log.log works *after* quitting s3sync Post by: ferrix on April 23, 2007, 11:13:43 AM Buffering of line output is probably controlled by your shell (that's what's hooking up the things together via the '>' operator)
Title: Re: s3sync --some_options >/path/to/log.log works *after* quitting s3sync Post by: maelcum on April 25, 2007, 11:20:46 AM Ok. Thanks.
Might well be. I've installed s3sync on a NAS-Box with ash (not bash) as a shell. I haven't noticed this behaviour with other commands, but then, those are "internal" in comparison to the ruby-calls. At least I'm sure now, that it isn't s3sync.rb. Topic closed. |