On Thu, 24.04.14 16:31, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> > > > I have added this now to the TODO list, but don't hold your breath... > > > I've been thinking about this too, and actually for the same usecase (i.e. > > > logs from X). I think we should teach various programs like X to logs an > > > equivalent of _BOOT_ID (e.g. "XORG_RUN_ID"), and then systemctl could be > > > extended to support it the same -b / --list-boots, except that the > > > user would specify the tag (e.g. XORG_RUN_ID) to sort on. The > > > advantage would be that e.g. Xorg and gdm could agree to use the same > > > tag for the same session, thus making is easy to correlate log > > > messages. > > > > Hmm, such an XORG_RUN_ID would be pretty close to _SYSTEMD_SESSION= > > then, no? > Yeah, but _SYSTEMD_SESSION repeats... It would be useful to have a randomized > tag too. _SYSTEMD_SESSION_ID? The idea was that it may be combined with the BOOT_ID and you'd then have a unique identifier... But the combination of the two fields would have to be client side... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
