Linux

You are reading a single comment by @NotThamesWater and its replies. Click here to read the full conversation.

•

aggi in reply to @NotThamesWater

Try adding a logfile output for more info on what is happening

Cheers, thinking about it this is probably my fundamental question. What's the best way of seeing what is happening? Is cron output logged somewhere or can I set it up to do this somehow, should I add a logfile to the cron command (just "> logfile" at the end I assume) or somewhere in the actual script (probably a bit beyond me)?

EDIT: cheers @Greenbank I'll give that a try and see what comes out.

•

NotThamesWater in reply to @aggi
There's an option in the script for creating a logfile (see lines 310 / 311) - just add "-L /somepath/somefilename" to your command

(There might even be a default rsync log somewhere in /var/log I suppose)

If you run the script manually (i.e. no from cron) you could also do what greenbank suggests

[Edit]

And I hate to be that guy, but: README.md
Options:
```
-l writes rsync log to 'sdimage'-YYYYmmddHHMMSS.log
-L logfile writes rsync log to 'logfile'
```

•

Greenbank in reply to @NotThamesWater

The only problem with a logfile option like that is that it won't log out problems with the script itself, those will only go to stdout/stderr and if cron can't find an MTA to send them on via email they're just being lost as they don't get logged anywhere else.

About

Avatar for NotThamesWater @NotThamesWater started