On Mon, Dec 20, 2010 at 09:03, Laine Stump <laine(a)laine.org> wrote:
There are two possible solutions for this:
1) Don't attempt to immediately read the pidfile and store the pid in
memory. Instead, just read the pidfile later when we want to kill
radvd. (This could still lead to a race if networkStart and
networkDestroy were called in tight sequence by some application)
In such tight sequence you can detect that radvd has been just
started, because radvd truncates pidfile before daemon(). In such
situation you can wait for pid awhile (e.g. separate thread could use
inotify for this)
Some general questions:
- radvd is optional for ipv6 network. How one can configure to not to
spawn radvd daemon
- did you thought about running only one instance of radvd and sending
SIGHUP to daemon after adding/removing interfaces to conffile
--
Pawel