> "Kinda hard to keep > a terminal window open on a headless server...)"
Not as hard as you'd think. I had a system set up to run as an IBM mainframe emulator (Project Hercules) and I needed to access its console for control purposes. It wasn't exactly a walk in the park, but you can accomplish marvellous things with "nohup" and "screen". I believe that the cron logging goes to /var/log/messages in the Debian/Ubuntu distros. /var/log/cron is a RedHat/Fedora thing. Red Hat tends to be a bit more granular in its logging. CRON tasks would normally email results to the cron queue owner (or root, for the global crontab), but you can override that in a cron setup. It never hurts to redirect stdout/stderr in a cron task to a file set aside for that purpose. Well, maybe sometimes it does, but not often. On Wed, 2010-11-10 at 16:59 -0500, Ephram wrote: > I keep forgetting Gmail likes to set the 'reply' to the specific person and > not the list... > > I'm running Lucid (10.04). There's no cron or cron.log in /var/log. In the > syslog, however, in the syslog, I only found: > Nov 10 16:30:20 tomatogoatee CRON[658]: (root) CMD > (/usr/bin/btdownloadcurses --saveas /shared/torrent /shared/a.torrent &) > > No error messages or anything. > > I know it isn't necessary to reboot every time, but I just like to be > thorough. > > This is getting a little ridiculous. Surely there'd be an easier way to > setup a dedicated, headless Linux torrent server. Google keeps running me > around in circles to the same forums with the same problem I'm having. (In > that all CLI torrent programs require a terminal window. Kinda hard to keep > a terminal window open on a headless server...) > > On Wed, Nov 10, 2010 at 4:32 PM, William L. Thomson Jr. < > [email protected]> wrote: > > > 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] > > > > --------------------------------------------------------------------- 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]
