Hi Greg, On Wed, Nov 17, 2010 at 05:28 AM PST, Greg Wooledge wrote: GW> On Tue, Nov 16, 2010 at 03:13:13PM -0800, Mun wrote: GW> > That's just it, I don't have any cron scripts that use here-documents. GW> GW> at jobs.
I don't have any 'at' jobs (that I know of). GW> > Most of my cron jobs are fairly trivial scripts less than 100 lines long. GW> GW> Not cron. (Unless RHEL's cron spits out emails that look like at's? I've GW> never seen a job ID number in a cron email.) GW> GW> > I'm running on a Red Hat Enterprise Linux 5.5 system, and my guess is GW> > that the system is running something on my behalf. But I don't know GW> > what. GW> GW> On HP-UX: GW> GW> List scheduled jobs: GW> at -l [job-id ...] GW> GW> at -l -q queue GW> GW> On Debian: GW> GW> atq [-V] [-q queue] I ran atq as myself as well as root an nothing showed up. So now I'm wondering what can possible create an at job on the fly. GW> > At first I was able to ignore the messages because I could not detect GW> > any anomalies. But now I've reached my threshold where the messages GW> > (sometimes up to about ten in a day) are starting to annoy me. GW> GW> Then you should have about 10 intervals per day to find a scheduled job. GW> (Hint: do it as whoever's receiving the e-mail.) Maybe I'll have to kick off a cron job to run atq until I can figure out the culprit. GW> You could also try to find the place on disk where the at jobs live. GW> It might be /var/spool/at (RH 5.2) or /var/spool/cron/atjobs (Debian 5.0, GW> HP-UX 10.20), or somewhere else entirely. Looked there; directory is empty. Thanks for the excellent suggestions. -- Mun
