On Sat, Sep 3, 2011 at 3:28 PM, Lennart Poettering <lenn...@poettering.net> wrote: > Well, the thing is that RD_TIMESTAMP is an optional feature anyway, and > not setting it has no ill effects on things at all. So I am not sure > what we'd win by supporting something half-way that is optional > anyway... > > What I'd like to avoid here is have people ship this as default in a big > scale, where they really should get the proper timestamps and nothing > else.
Ok. I guess that's fair enough. > If it really bothers people so much that this tool is built from the > systemd tree I'd suggest they add a feature to /bin/date to format > CLOCK_REALTIME and CLOCK_MONOTONIC as integer. I am sure the maintainers > of coreutils would accept such a patch (it appears CLOCK_REALTIME is > already supported to some degree anyway with +%s, so a tiny patch for > CLOCK_MONOTONIC shouldn't be that hard.). Whether you patch systemd like > this or coreutils shouldn't really matter, except that with coretuils > you'd get a correct solution and with /proc/uptime support in systemd > you don't. Thanks for the suggestion. I'll either submit a patch to coreutils/busybox to do this or just wait for systemd to achieve world domination ;-) Cheers, Tom _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
