This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: RE: updatedb problem From: "Russell W. Behne" <russ@behne.stafford.va.us> Date: Mon, 21 Jun 1999 14:47:32 -0400 (EDT) Today, Michael J. McGillick thusly expounded: > What cron job is this? Which folder is it located in? I looked in the cron > folders in /etc, and saw something related to slocate, but nothing about > updating the database. That's it! Do: ls -l `which updatedb` and you'll see that updatedb is now a link th the new program that's replacing it: slocate. > This is the exact problem I was running into as well, (see my email on > possible race condition with amd and updatedb). Updatedb has always > worked before, with no command line arguments necessary. Did something > change with the new kernels or Linux that now requires arguments to be > added? Yes. (ibid, and do "man slocate") === Subject: Re: Cron <root@behne> run-parts /etc/cron.hourly From: Ramon Gandia <rfg@nook.net> Date: Mon, 21 Jun 1999 21:56:19 +0000 Russell W. Behne wrote: > > I'm using: > # rpm -q bash > bash-1.14.7-16 > > I've been trying to track the problem. I followed it to: > /etc/cron.hourly/inn-cron-nntpsend > > Which runs: > #!/bin/sh > /sbin/chkconfig innd && su - news --command=/usr/bin/nntpsend > > If I run the above manually "/sbin/chkconfig innd" runs ok, but "/su - > news --command=/usr/bin/nntpsend" causes the -c error message. > > /usr/bin/nntpsend is a bash shell script, but I don't yet understand > enough bash to determine just what's happening. > > I've tried changing "--command=/usr/bin/nntpsend" to "-c > /usr/bin/nntpsend" but it made no difference. I also changed su to use the > full pathname, again no difference. You must be a large ISP to need nntp. That is the server for usenet news, typically handles 2 GB of data every single day coming in your T3 line. :-) Oh...if you are not an ISP with a news server, you should not run NNTP. Its one of those things that RedHat, in their infinite wisdom, likes to have newbies install and run. Be sure to deactivate NNTP in your cron hourly as well as in /etc/rc.d/init.d files. === Subject: Re: Cron Help From: Bill Carlson <wcarlson@vh.org> Date: Thu, 9 Dec 1999 16:17:33 -0600 (CST) On Thu, 9 Dec 1999, Todd Dunbebin wrote: > I'm trying to get my linux box to synch with a time server, and I'm trying > to use crontab, this is what I hve in the file settime > and I issue the command: > crontab /root/settime > and it looks like it accepts it but I keep getting errors emailed to me, > anyone know if the syntax is screwy or something? I was also trying to run > one to write the clock to the bios (battery's going I think) > > > * /15 * * * * /usr/bin/rdate -s bitsy.mit.edu > > it is: > /15 * * * * * /sbin/clock -w > > any help? A better way, I've searched all over for crontab syntax and have > found little at best. You seek a good man page, one which is not the default... [wcarlson@ryoko wcarlson]$ man -k cron cron (8) - daemon to execute scheduled commands (Vixie Cron) crontab (1) - maintain crontab files for individual users (V3) crontab (5) - tables for driving cron man 5 crontab That is what you seek, all the info you ever wanted. ===