Bug 4770 - Change of pidfile creation
Change of pidfile creation
Status: RESOLVED WORKSFORME
Product: Samba 3.0
Classification: Unclassified
Component: Build environment
3.0.25b
Other AIX
: P3 trivial
: none
Assigned To: Tim Potter
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-10 04:12 UTC by Chris Paulheim
Modified: 2019-01-24 01:05 UTC (History)
0 users

See Also:


Attachments
CHange the alternitave Pid FIle name (558 bytes, patch)
2007-07-10 04:14 UTC, Chris Paulheim
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Paulheim 2007-07-10 04:12:15 UTC
Hello Samba Team, 

in our Company we use samba on AIX with HACMP. For using more instances we have patched the source code of pidfile.c in source/lib directory. 

The Filename of the Pidfile(with alternative Conf File) will be created with the follwing fields: <programname>_<NAME of Conffile without .conf>.pid 

In the old varainte the name was like: <programname>-<conffilename with .conf>.pid 



The patch change only the pidfilename, so that it look better.
Comment 1 Chris Paulheim 2007-07-10 04:14:16 UTC
Created attachment 2805 [details]
CHange the alternitave Pid FIle name
Comment 2 Björn Jacke 2008-02-12 15:47:47 UTC
this is implemented in the current samba release now in a similar way
Comment 3 Chris Paulheim 2008-02-13 02:34:00 UTC
the pid file will be still created with the full .conf File name

root@xxxxx# ls -l /var/run/samba/inst01/smbd-smb_inst01.conf.pid
-rw-r--r--   1 root     system            7 Feb 13 09:20 /var/run/samba/inst01/smbd-smb_inst01.conf.pid
root@xxxxx# smbd --version
Version 3.0.28


Comment 4 Björn Jacke 2019-01-24 01:05:38 UTC
the functionality of having the config file being part of the pidfile got lost with the merge of the source3 and source4 trees in the 4.0 series. It could be a nice thing to have but it was also a bit complex and could confuse a bit. Someone ho needs this can achieve the functionality also by setting a different "pid directory" option for different instances of the same daemon process, right? I'm closing this for now again, feel free to reopen if you think "pid directory" cannot handle it.