> > > > 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. Also note that klibc doesn't implement IPC, so ha_logd would not fit your goals as-is. Regards, cvaroqui
