On Thu, 03.03.11 09:14, Andrey Borzenkov (arvidj...@gmail.com) wrote:
On Thu, Mar 3, 2011 at 7:51 AM, Andrey Borzenkov arvidj...@gmail.com wrote:
On Thu, Mar 3, 2011 at 12:31 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 02.03.11 11:41, Andrey Borzenkov
On Thu, 03.03.11 07:51, Andrey Borzenkov (arvidj...@gmail.com) wrote:
On Thu, Mar 3, 2011 at 12:31 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 02.03.11 11:41, Andrey Borzenkov (arvidj...@gmail.com) wrote:
It is expected that system will put reboot in wtmp to mark
when
On Thu, Mar 3, 2011 at 6:20 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Thu, 03.03.11 09:14, Andrey Borzenkov (arvidj...@gmail.com) wrote:
On Thu, Mar 3, 2011 at 7:51 AM, Andrey Borzenkov arvidj...@gmail.com wrote:
On Thu, Mar 3, 2011 at 12:31 AM, Lennart Poettering
It is expected that system will put reboot in wtmp to mark
when it starts coming up. This is looked for by who -b and is
used by last to calculate correct time spent by various programs.
Add systemd-update-utmp-reboot.service which is started as soon
as possible after local-fs.target to mark
On Wed, 02.03.11 11:41, Andrey Borzenkov (arvidj...@gmail.com) wrote:
It is expected that system will put reboot in wtmp to mark
when it starts coming up. This is looked for by who -b and is
used by last to calculate correct time spent by various programs.
Add
