Re: bootlogd
On Fri, 28 Oct 2011 23:14:46 +0100, Bob Brewer wrote:
> Camaleón wrote:
>
>>> On my up-to-date sid distro, my /var/log/boot hasn't been updated
>>> since 13 April 2011 (BOOTLOGD_ENABLE is set to Yes in
>>> /etc/default/bootlogd).
>>>
>>> This looks to be the same as Bug 624289 which was raised against the
>>> sysvinit-utils package but perhaps should have been raised against the
>>> initscripts package.
>>
>> Mmm, in wheezy it works fine, maybe because I have "2.88dsf-13.12"
>> version for "sysvinit-utils" package :-?
>>
>>
> I think that is the same package version for sid. What version of
> initscripts is wheezy running, my version is also "2.88dsf-13.12". If
> yours is the same then I'll need to look for other causes.
You're right... it seems sid and wheezy share the same version.
"initscripts" package is also "2.88dsf-13.12".
>>> I haven't been able to find any workarounds to run bootlogd at boot
>>> time and need to look at my boot data so I would be interested to know
>>> if there any alternatives to bootlogd.
>>
>> "/var/log/boot" file is almost empty because boot messages are splitted
>> in two separate files (kern.log for "kernel" messages and boot for the
>> "services" part).
>>
> Nothing has been written to my 'boot' file since last April so I guess
> something was changed during a software update since then, I haven't
> knowingly turned of boot logging.
(...)
Mmm... are the kernel logs being written okay? Have you a separated "/
var" partition?
Greetings,
--
Camaleón
Reply to: