On Wed, 2009-09-02 at 12:15 +0100, Colin Watson wrote: > I can't say I'm keen on an arbitrary delay either. inotify would be > better, but until rsyslog can use it perhaps
I have checked the code now. What I can do with relative ease is re-try opening failed sockets. However, this would create a non-deterministic delay, because - with the current code - this would only happen after select() is left, that is after one message on at least on of the active sockets has been received. I doubt this is really useful... On the other hand, in the case of a system start, chances are good to have such a message relatively soon, so it may be a pretty dirty but useful change, in the sense that it works most of the time... Let me phrase a question on inotify: you would use it to watch the directory if the sockets has been created (and recursively watch all directories above it, if they do not exist OR disappear during the watch process)? Or am I overlooking something. I have to admit I have not really used inotify so far (compatibility...) so I may be overlooking something or may be thinking too complex. Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org