Peter Worboys wrote:
>
> > Terry Collins:
> > Since the logging is specified in the .fetchmailrc file, it should not
> > matter whether it is in daemon mode or not.
>
> Terry
>
> Yes you are 100% correct, you can use the --logfile command line or the 'set
> logfile' in the rc file, but this produces a pretty brain-dead log giving no
> times/dates. i.e.:
>
> fetchmail: starting fetchmail 4.5.8 daemon
> fetchmail: 232 messages (229 seen) for pworboys at 172.30.65.31 (348770
> bytes).
> fetchmail: skipping message 1 not flushed
> fetchmail: skipping message 2 not flushed
> ....
> fetchmail: reading message 231 of 232 (762 bytes) . not flushed
> fetchmail: reading message 232 of 232 (897 bytes) . not flushed
I usually combine this with two batch files;
tfm tail fetchmail.log which tells me if stuff is coming in, and
fm fetchmail which just kicks fetchmail off if there is a
problem shown above and usually inserts a fetchmail daemon message.
Usually, this is enough to alert me to the fact that my permanent
modem link has disconnected (all three external mail address are not
accessable), or if my ISP has routing/link probelms (two externals are
not accessible).
What about /var/log/messages? Will that give you what you want?
--
Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861
email: [EMAIL PROTECTED] www: http://www.woa.com.au
WOA Computer Services <lan/wan, linux/unix, novell>
snail: PO Box 1047, Campbelltown, NSW 2560.
"People without trees are like fish without clean water"
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
