Package: logjam
Version: 4.5.3-1+b1
If 'logjam offline sync' cannot connect to a remote server it issues an
error message to stdout and exits with status 0.
It should:
- send error messages to stderr rather than stdout. Then it would
be possible to suppress normal progress messages with >/dev/null
while still seeing error messages.
- exit with a nonzero status when something goes wrong. Then scripts
can detect errors and take appropriate action.
The immediate use case is running 'logjam offline sync' from cron: at
the moment there is no way to ensure that it only produces output (and
thus email) when something goes wrong. However the above rules are
necessary for all kinds of scripting.
ttfn/rjk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
