Hi
I think I understand (ish?)
what is happening is this ...
When I run the invoke-rc.d exim4 stop
I check with ps -ef and there is still an exim process running
[115 14932 1 0 Oct17 ? 00:00:00 /usr/sbin/exim4 -bd -q30m]
(is this a daemon ?)
I am still able to send e-mail using my outlook client from a remote machine
in fact this very e-mail has been sent using outlook express immediately
after doing a stop ...
After having read the replies I am not sure if this is correct behaviour ?
what I do know is that now if I run an invoke-rc.d exim4 start
I get errors saying port 25 already in use
[2006-10-18 12:01:29 socket bind() to port 25 for address (any IPv6) failed:
Address already in use: waiting 30s before trying again (9 more tries)]
and ps -ef shows two exim processes running ...
115 14932 1 0 Oct17 ? 00:00:00 /usr/sbin/exim4 -bd -q30m
root 18514 1 0 12:01 ? 00:00:00 /usr/sbin/exim4 -bd -q30m
If I do another "stop" they are both still there
What you could probably better answer for me is ...
If I make a change to my configuration file do I need to stop and start the
process for the change to take effect ?
Many thanks in advance
Hill Ruyter
----- Original Message -----
From: "W B Hacker" <wbh@???>
To: "exim users" <exim-users@???>
Sent: Wednesday, October 18, 2006 10:45 AM
Subject: Re: [exim] re [TLS Problem]
> Philip Hazel wrote:
>
>> On Tue, 17 Oct 2006, Hill Ruyter wrote:
>>
>>
>>>When I stop exim (I use invoke-rc.d exim4 <stop> <start>)
>>>I find that there is still a process running for exim after I have
>>>stopped
>>>it
>>
>>
>> All you are stopping is the Exim daemon. Other Exim processes that
>> happen to be running (receiving a message, delivering a message) are not
>> affected. Because of the way Exim is designed, there is no concept of
>> "stopping Exim". Analogy: think about something like telnet or ssh. You
>> can stop the daemon that listens for incoming connections, but there is
>> no concept of "stopping telnet" or "stopping ssh" - i.e. of preventing
>> the command "telnet" or "ssh" from being run. Similarly, you can't stop
>> a person or process from running /sbin/exim (or whatever the binary is
>> called). The daemon is not needed to receive a local message or do
>> deliver it (either locally or remotely). The only way to prevent that
>> happening is to remove the command, or break the configuration.
>>
>
> That is precisely what is required IF/AS/WHEN, for example one is tailing
> the
> log of an experimental configuration and spots a serious glitch that
> might/has
> left a relay-hole:
>
> killall exim-4.63-0
>
> ...doing the same to sshd, OTOH, means one had best have *very long arms*
> or
> responsive site-techs if the server is not close by..
>
> ;-)
>
> Bill
>
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
>
