Open GoogleCodeExporter opened 9 years ago
hm runs a custom Lusca build with some tproxy patches but he tells me it
happens with
a clean, non-tproxy patched Lusca.
He also mentioned that it happens only at startup. It doesn't happen if he
manually
runs the startup scripts himself.
It doesn't occur on my local FreeBSD-8.0-p2 amd64 box with the lusca-head port.
I had a theory - that SIGHUP is being received shortly after startup because of
SIGHUP being sent to the process group.
A bit of digging showed that Lusca doesn't disassociate from the current process
group and create its own if it's run with the -N (no daemon) flag.
I asked him to add a call to setsid() at the beginning of mainInitialize(). This
fixed his issue.
The question now is why -his- setup is generating process group SIGHUP's which
aren't
appearing elsewhere.
Original comment by adrian.c...@gmail.com
on 5 Apr 2010 at 10:19
Original issue reported on code.google.com by
hm@hm.net.br
on 5 Apr 2010 at 10:14