On Tue, 2005-03-22 at 17:11 +0100, Christophe Varoqui wrote: > > > > > > Does your log.[ch] implementation works around syslog blocking behaviour in memory contention situation ? > > > > yep syslog sucks. > > as of now, our logger still based on syslog. its missing some stuff. > > There is another logger which proved to work under memory pressure - > > ha_logd from HA project. if I will have time, I'll merge some stuff from > > ha_logd to log.[ch]. > > > > > If so, I would like to fetch it in multipath-tools, with your agreement. > > > Also, if you have better ideas on the subject, I'm interested in reading them :) > > > > so, try ha_logd. Also I saw in your code mlockall() right after > > syslog(). Could you explain why we need it? I think just one call at the > > beginning phase should be enough unless you fork? > > > I looked that code, but there are a number of non-trivial dependencies to remove to make the code self-contained and generic : glib.h and cl_*.h come to mind. yep. life is not fair... > Also note that klibc doesn't implement IPC, so ha_logd would not fit your goals as-is. i'm thinking about utilizing NETLINK protocol. In open-iscsi we using it to implement protocol level IPC. We can try to come up with ipc-based log implementation which will be based on ha_logd and will be generic enough for both dm-multipath and open-iscsi. Dima > > Regards, > cvaroqui > > -- > > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel
