Simo Sorce wrote: > On Mon, 2009-10-12 at 12:10 -0400, Dmitri Pal wrote: > >> Yes this way it is standard. I thought you wanted to pass a socket >> between processes later after fork. >> But here is the question. If you have multiple children writing to the >> same fd at the same time how you then sort which one has written what. >> Would it be better to have a log per child process instead and have a >> pid appended to the name of the log file than all output in one file >> mixed? >> It is usually hard to read and debug when everything is mixed in one >> file. >> > > This is used only for debugging, we can stand some mixed inputs there to > keep the thing simple, however in the children we can change the debug > function to always print the PID on every debug message, so that at > least it should be clear where messages came from. > > Simo. > > Yes we can add pids to every line but from my experience such logs are very hard to read when debugging a program. You have a mixture of relevant and irrelevant information in one sequence of lines. IMO it is very annoying and hard to process.
-- Thank you, Dmitri Pal Engineering Manager IPA project, Red Hat Inc. ------------------------------- Looking to carve out IT costs? www.redhat.com/carveoutcosts/ _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel