[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to access mailserver

On 15 Jul 1999, Martin Bialasinski wrote:

> A) you run exim in daemon mode
>    check with ps ax| grep exim that it is running.
>    /etc/init.d/exim restart -> errors?
No, exim doesn't run, because this would differ from the default,
which I left untouched because of less knowledge in that field.
Moreover /etc/init.d/exim starts with:

# Usually this is disabled and exim runs from /etc/inetd.conf
exit 0
Deleting this line I can start exim successfully and fetchmail works
correctly.  Now my question is, and in my opinion I'm right now
back on the development tree of this question and do legally
posting here, why is this not done by default?

When configuring exim I configured it for uses which was recommended
together with tools like fetchmail.  WHat is the advantage of
starting exim via inetd (or to say better *NOT* starting it via
inetd) instead of running exim as daemon?
Moreover I wonder how inetd should know about exim?
/etc> find . -type f -exec grep -l exim \{\} \;

There is no exim call anywhere because /etc/init.d/exim stops
immediately and the cron jobs do only periodically start.
I consider it to be hard for the unexperienced user (obviosely
I count to this set in the topic of configuring a working
e-mail) to get it work and we should simplify this, which
is importand for any modem user.

> B) you are running exim from a superdaemon
>    check in inetd.conf or xinetd.conf that it is enabled
>    kill -SIGHUP `pidof inetd` or xinetd and check the syslog or daemon 
>    log for errors
There where no errors in the syslog or daemon log.  (To say the
trouth I didn't do the killing process you mentioned, but I think
I tried it often enouth also between some reboots for other purposes
that any errors should have been printed into the logs.)
> I have set a Reply-to to debian-user as it is the more appropriate
> list for this I believe.
As I said, I think we are back and my apologies once more for
posting to the wrong list.  Moreover I havn't got any reply
from debian-user-request yet and want to solve this problem

Kind regards


Reply to: