Re: Mail and news
>>Have a look at /var/spool/smail/log/logfile and
>>/var/spool/smail/log/paniclog to see if Smail has anything to tell
>>you.
>
>bash# ls -l logfile
>-rw-r--r-- 1 root root 0 Feb 16 07:03 logfile
>bash#
>
>bash# ls -l paniclog
>-rw-r--r-- 1 root root 0 Feb 16 07:03 paniclog
>bash#
That means the mail system hasn't done anything whatsoever today...
try sending a mail message and see what you get in these files. I'm
trying to establish what trouble the mail system is running into.
If you have multiple VCs or xterms then you can leave e.g.
tail -f logfile
running in one and do things with the mail system in the other, thus
seeing the log messages as they happen.
>Ah. the logfile.0 has a little more useful information:
>
>02/15/96 11:06:48: open_spool: /var/spool/smail/input/0talp0-0008spC: lock fail
>ed: Try again
>
>02/15/96 11:07:54: open_spool: /var/spool/smail/input/0tbD4n-00091DC: lock fail
>ed: Try again
That's generally what happens when two queue runs try to happen at
once e.g. if you type `runq' twice in quick succession. There may be
other conditions in which it can occur, though.
>More information available if this isn't enough.
You're going to have to tell us all the information you have - the
Smail configuration files and what mechanism you're expecting the
machine to use, as discussed in my previous message in this thread.
--
Richard Kettlewell (hoping to crack this one in the end...)
http://www.elmail.co.uk/staff/richard/ richard@uk.geeks.org
Eat a live toad before breakfast and nothing worse will happen to you all day.
Reply to: