Mailing List Archive: [Bug 403] second zebra server keeps latter zebra clients from connecting to the first one

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.quagga.net/show_bug.cgi?id=403

------- Additional Comments From web@pilot.org.ua 2007-10-30 12:54 -------
Of course, the problematic case is the UNIX socket one. zebra_serv_un() removes
any existing socket before creating a new one, thus blocking any further
connection attempts to the previous copy of zebra daemon.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.

http://bugzilla.quagga.net/show_bug.cgi?id=403

web@pilot.org.ua changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|CVS |0.99.9
Status|NEW |ASSIGNED

------- Additional Comments From web@pilot.org.ua 2007-10-30 12:51 -------
The problem is reproducible an all systems, which use TCP zebra socket instead
of UNIX socket. In particular, my FreeBSD system by default chooses UNIX socket
as opposed to my Linux system which sticks with the TCP socket.
The root cause of the problem is that zebra_serv_un() is called unconditionally
before acquiring the pidfile lock. This misbehaviour is very similar to the one
I have already fixed WRT removing pseudo-own route records from the FIB. Will
look into this deeper later.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs