[ic] Restart and stop problems (multilple processes)
Mike Heins
interchange-users@icdevgroup.org
Wed Feb 5 18:09:00 2003
Quoting Daniel Hutchison (jdhutchison11@attbi.com):
> On Wed, 2003-02-05 at 14:41, Mike Heins wrote:
> >From what I can tell, the problem seems to be in the locking of the pid
> file. Eg. interchange attempts to lock the pid file when it starts up.
> If it can't lock the pid file, it assumes another interchange process is
> running. What I suspect is that interchange locks the pid file before
> it forks. Since on solaris, locks created with flock() aren't inherited
> across forks. As a result, when the parent process exits the pid file
> becomes unlocked. When interchange is then run with the shutdown
> command it detects that the pid file unlocked and thinks that there
> isn't a running interchange process.
>
> What I have done is verify that the default install of interchange on my
> solaris box uses the flock() function to lock the pid file. I've also
> created a mini perl program that just locks files based off the code in
> interchange. The file locking works fine until I throw a fork() in
> it...
This begs the question -- what Perl? Has an update to Perl 5.8 been tried?
I believe changes have been made to improve this in the latest version.
Also, have you tried:
LockType fcntl
in interchange.cfg?
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.513.523.7621 <mike@perusion.com>
Friends don't let friends use Outlook. -- Bob Blaylock