On Tue, 03.06.14 11:21, Łukasz Stelmach (l.stelm...@samsung.com) wrote: > It was <2014-06-01 nie 07:52>, when Lennart Poettering wrote: > > On Fri, 30.05.14 12:45, Piotr Wilczek (p.wilc...@samsung.com) wrote: > > > >> This patch adds posibility for journal to get process data from > >> socket data (if available) instead of from procfs. > >> > >> Additionally a new procinfo structure is added to store all process > >> data in single place. This data include creditentials and status. > >> > >> To enable this functionality, SO_PASSPROC socket option must be set. > >> This option is introduced in: > >> http://lwn.net/Articles/600564/ > > > > I really *love* this work! It would be fantastic if we could get this done. > > > > Hmm, I am not seeting that SO_PASSPROC is actually turned on in this > > patch? Am I missing something? This really needs to be an option that > > can be turned on from the sending side, otherwise it would be only half > > as useful... > > "sending side"? Do you mean a daemon have to turn it on? IMHO it is > systemd's job to set up a socket for service to log to, or journald's job > to "request" this info to be passed to it. What am I missing?
Sorry, it was too early that day for my brain to fully function. Of course, I meant that the *receiving* side must be able to turn this on, not the sender, so that journald can turn it on, and it just works for any client. Sorry for the confusion! Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
