Probably would help to clarify Linux distro for logs and other suggestions below.
On Wed, 2010-11-10 at 16:24 -0500, Ephram wrote: > Changing the path to /usr/bin/btdownloadcurses doesn't start it > either. What log files should I be checking for cron? That can vary per system some are /var/log/cron /var/log/cron.log /var/log/syslog /var/log/syslog.log /var/log/messages /var/log/daemon.log > (FYI, I'm initiating a reboot command every time I change the crontab, > just to make sure the program would start on boot.) Thats totally not necessary, no need to reboot Linux unless your changing kernels. > Heck, at this point I'd be happy with a command that would let me > start the torrent then log out of the system. btdownloadcurses and > btdownloadheadless both quit when you exit... I would recommend using an init script if this is something your trying to do on boot. Or if your doing it via cron, something thats going to check to see if the command is running, if not run it. Cron is not ideal for running something on off at a particular interval, or on boot. Init scripts are best for actions you want to take on boot. Programs like at, can be used to schedule something to be run ones at a particular time. If its something you want to start on boot, init script. If it can fail after, maybe a cron job with a script to check if its running and start it not. Which would likely involved re-invoking the init script. Init scripts are distro specific, but you can usually find some examples if you google. Or can ask and some can be provided here I am sure :) -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
