On Tue, 19 Nov 2002 12:12:06 +0300, Odhiambo Washington wrote:
>* Ralf G. R. Bergs <rabe@???> [20021119 11:52]: wrote:
>> On Tue, 19 Nov 2002 11:39:46 +0300, Odhiambo Washington wrote:
>>
>> >> Server:~# exim -C /etc/exim/exim.conf -bP spool_directory
>> >> No permissions to read config file (null)
>> >
>> >what does a simple `exim -bP` give??
>>
>> Same thing:
>>
>> Server:~# exim -bP
>> No permissions to read config file (null)
>
>This tells me that you will have to build Exim again. This time round
>you have to make a lot of decisions on the EXIM_USER and possibly
>EXIM_GROUP from the Local/Makefile. I am assuming you compiled Exim
>by hand.
No, I did not build it by hand. I used a Debian package I created myself by
migrating the old Exim 3.xx Debian package.
And as I wrote earlier the daemon is running GREAT, so I don't think there's
something wrong with uid/gid settings.
>> Well, it's not me specifying the config file, but it's inside
/usr/sbin/exiwhat.
>
>I don't understand this, so I will leave it alone. There is no problem with
>exiwhat that I know of.
I'm not implying that there is a problem with exiwhat, I'm just saying that
the "-C /etc/exim/exim.conf" setting is inside exiwhat.
>Q1. Does the file /etc/exim/exim.conf exist? What are the permissions on it?
644.
>Q2. How did you build/install your Exim? This is most important.
See above. The daemon can read it properly when starting up. Why should this
be different when invoking exim as "-bP"? Can you explain me the strange
"strace" output?
--
L I N U X .~.
The Choice /V\
of a GNU /( )\
Generation ^^-^^
