On Thu, Mar 10, 2005 at 01:31:10PM +1300, Jason Haar wrote:
> Hi there
>
> I am running two instances of nessusd - on different ports. However, I
> am having problems, and I've dug out something that isn't right...
>
> It looks like nessusd is hardwired for several paths: the pid and
> "state" directory are embedded in the binary. This makes me wonder
> what's meant to happen when a HUP/whatever is sent - which one of the
> two nessusd processes gets it? (the answer is "only one of them").
Nessus is not meant to be launched multiple times in parallel.
If you really want do so then you need to compile twice, under two
different prefixes.
> Shouldn't the pid location - or at least the statedir be a config
> option?
No. The assumption when I code is that $localstatedir belongs to me and
I can write anything I want in it. $localstatedir being a #define, it's
not configurable at run-time.
If I start to add config options for every item I want to add (in the
present[*] or in the future), then it introduces good odds
breaking stuff.
-- Renaud
[*] ie: this is where the BPF server creates its Unix socket under BSD
systems.
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
