Hi Helmut,

are you using the same socket name for both openser's ?

Regards, Bogdan

Helmut Kuper wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I found that starting a 2nd openser with same config as a already running openser on same machine and using module mi_datagram deletes the socket file of the already running openser process.

This is very bad when u use openser as a frontend for sems for example. :(

Is this a bug or a feature? If it is a bug the check, whether there is already a openser using same network resources should be befor starting modules. Or modules should be able to handle those problematic scenarios ...

My mi_datagram conif ist this:

loadmodule "mi_datagram.so" modparam("mi_datagram", "socket_name", "/tmp/openser_ansagen_sock") modparam("mi_datagram", "children_count", 1) modparam("mi_datagram", "unix_socket_mode", 0660) modparam("mi_datagram", "unix_socket_group", "voip") modparam("mi_datagram", "unix_socket_user", "ruth") modparam("mi_datagram", "socket_timeout", 2000)

regards Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHsBIl4tZeNddg3dwRAgzVAJwKfUdqhd8oEm5eFewAflnosmofYQCgibYC WjR2C9pf0FIxJjD5JewRPww= =0roh -----END PGP SIGNATURE-----

---

Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users