[Mailman-Users] mailman v2.1.20 init script for cos7 / wrong pid location

[fsantiago at garbage-juice.com]

Mark,

thanks for your reply. But i believe you misunderstood; all files have 
been taken from the source distribution (or were put in their current 
locations during 'make install'). I have used no packages in this 
endeavor.

I double checked and ran diff; <source>/misc/mailman and 
/etc/rc.d/init.d/mailman are an exact match. they should be as i put it 
there today myself.

so, what else?

- Fabe S.


On 2015-10-06 14:13, Mark Sapiro wrote:
> On 10/06/2015 10:30 AM, fsantiago at garbage-juice.com wrote:
>> 
>> I've installed / compiled mailman 2.1.20 from source on centos 7. 
>> works
>> fine when manually operated via:
>> 
>> bin/mailmanctl start / stop
>> 
>> when i copy the mailman script from /scripts to /etc/rc.d/init.d and
>> perform 'chkconfig --add mailman', and then try to start it via:
> 
> 
> You should be using the configured init.d script from misc/mailman in
> the directory in which you configured the source distribution.
> 
> 
>> systemctl start mailman
>> 
>> it does actually start (I can see the processes) but on the CLI, it
>> reports start failed. When I ask for the status, it tells me:
> ...
>> Now, the readout states the pid file as
>> /usr/lib/mailman/data/master-qrunner.pid, which doesn't exist.
>> 
>> When started manually via mailmanctl, the pid file that is created is:
>> /var/lib/mailman/data/master-qrunner.pid
>> 
>> When started via systemctl, despite the reported error, the pid file
>> actually exists under /var/lib...
>> 
>> So systemd is looking in the wrong spot for the pid apparently.
>> 
>> Where can I make a change to tell systemd where to look? Thanks 
>> everyone.
> 
> 
> Probably in something like /etc/sysconfig/mailman, but if you want to
> run the source distribution, you should be using it 100%. If you 
> install
> from source but use init.d scripts, crontabs, etc. from a package,
> you're asking for trouble.