[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple isakmpd's.
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: multiple isakmpd's.
- From: Janne Johansson <jj_(_at_)_dynarc_(_dot_)_se>
- Date: Fri, 22 Dec 2000 10:19:11 +0100
- Reply-to: jj_(_at_)_dynarc_(_dot_)_se
> How about just having your crontab job start by checking if
> PID `cat /var/run/isakmpd.pid` still exists? Simple enough.
> I don't recall the rationale behind isakmpd 'hanging around' (especially
> since there does not currently seem to be a way to "reinitialize" those
> parts... although a SIGHUP will, for example, reread the configuration
> file), but I'll see what I can find.
I have gotten lots of replies about this.
I just want to clarify a bit.
I don't want to parse "ps" output, since sometime in the
really really remote future, one might want to have two
isakmpd's running with different configs running on
different ports. I also don't want to monitor a pid-file,
since it might not be removed if it segv's, right?
As of now, both ps-watching and pid-file checks would work for
me, yes, and I can build scripts to do just that (thanks to all
who volunteered ;-) but I was wondering if this was the desired
behaviour at all, for isakmpd. And no, I can't reliably crash
it, it just sometimes isn't there after I haven't used it for
some 5+ days.
BTW, I have had more luck with the 30-day eval of PGPnet
(6.5.4 I think?) than the commercial version 7 when doing
insecure-net-behind-secure-gateway. Anyone else tried v7 ?
Allt är under kontroll, och Caps lock är bredvid.
Visit your host, monkey.org