Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Debian GNU/Linux wheezy/sid - Howto setup bootlogd?
57 views
Skip to first unread message
Csanyi Pal
Jun 28, 2012, 11:00:01 PM6/28/12
to
Hi,
on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
BOOTLOGD_ENABLE=Yes
but the /var/log/boot
file has timestamp dec 27 2011
so it seem's that bootlogd doesn't work. Why not?
--
Regards from Pal
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/87fw9ea...@gmail.com
on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
BOOTLOGD_ENABLE=Yes
but the /var/log/boot
file has timestamp dec 27 2011
so it seem's that bootlogd doesn't work. Why not?
--
Regards from Pal
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/87fw9ea...@gmail.com
Dom
Jun 29, 2012, 2:30:01 AM6/29/12
to
On 29/06/12 03:53, Csanyi Pal wrote:
> Hi,
>
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
>
This may sound like a silly question, but do you have the bootlogd
> Hi,
>
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
>
package installed?
I ask, because around that time bootlogd was split off from
sysvinit-utils into a seperate package, which isn't installed by default.
dom@oz:~$ zcat /usr/share/doc/sysvinit-utils/NEWS.Debian.gz
bootlogd has moved from sysvinit-utils to a separate bootlogd
package. If you wish to continue using bootlogd, please install the
bootlogd package.
Note that the configuration file /etc/default/bootlogd and its option
BOOTLOGD_ENABLE no longer exist; if you do not wish to run bootlogd,
remove the bootlogd package.
-- Josh Triplett <jo...@joshtriplett.org> Mon, 19 Dec 2011 12:03:08
+0000
--
Dom
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andrei POPESCU
Jun 29, 2012, 2:30:01 AM6/29/12
to
On Vi, 29 iun 12, 04:53:53, Csanyi Pal wrote:
> Hi,
>
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
bootlogd is now in a separate package and the /etc/default/bootlogd is
> Hi,
>
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
not needed anymore (if you want it you install the package ;) it's safe
to delete it.
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
Csanyi Pal
Jun 29, 2012, 3:20:02 AM6/29/12
to
Dom <to...@rpdom.net> writes:
> On 29/06/12 03:53, Csanyi Pal wrote:
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>>
>
> This may sound like a silly question, but do you have the bootlogd
> package installed?
Indeed, I haven't installed the bootpogd package so I install it right
> On 29/06/12 03:53, Csanyi Pal wrote:
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>>
>
> This may sound like a silly question, but do you have the bootlogd
> package installed?
away.
> dom@oz:~$ zcat /usr/share/doc/sysvinit-utils/NEWS.Debian.gz
>
> bootlogd has moved from sysvinit-utils to a separate bootlogd
> package. If you wish to continue using bootlogd, please install the
> bootlogd package.
> Note that the configuration file /etc/default/bootlogd and its option
> BOOTLOGD_ENABLE no longer exist; if you do not wish to run bootlogd,
> remove the bootlogd package.
--
Regards from Pal
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
Jun 29, 2012, 10:10:02 AM6/29/12
to
On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
I'm in the same situation that yours.
> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
> BOOTLOGD_ENABLE=Yes
>
> but the /var/log/boot
>
> file has timestamp dec 27 2011
>
> so it seem's that bootlogd doesn't work. Why not?
AFAIK, the current implementation of bootlogd is broken, it does not work
though it did (sometimes) time ago.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Csanyi Pal
Jun 29, 2012, 10:50:01 AM6/29/12
to
Camaleón <noel...@gmail.com> writes:
> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>
> I'm in the same situation that yours.
>
> AFAIK, the current implementation of bootlogd is broken, it does not work
> though it did (sometimes) time ago.
I solved the problem by installing bootlogd package.
> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>
> I'm in the same situation that yours.
>
> AFAIK, the current implementation of bootlogd is broken, it does not work
> though it did (sometimes) time ago.
--
Regards from Pal
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
Jun 29, 2012, 11:00:02 AM6/29/12
to
On Fri, 29 Jun 2012 16:44:12 +0200, Csanyi Pal wrote:
> Camaleón <noel...@gmail.com> writes:
>
>> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>>
>>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>>> BOOTLOGD_ENABLE=Yes
>>>
>>> but the /var/log/boot
>>>
>>> file has timestamp dec 27 2011
>>>
>>> so it seem's that bootlogd doesn't work. Why not?
>>
>> I'm in the same situation that yours.
>>
>> AFAIK, the current implementation of bootlogd is broken, it does not
>> work though it did (sometimes) time ago.
>
> I solved the problem by installing bootlogd package.
Uh? This has been installed since... wait, you're right, the package is
> Camaleón <noel...@gmail.com> writes:
>
>> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>>
>>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>>> BOOTLOGD_ENABLE=Yes
>>>
>>> but the /var/log/boot
>>>
>>> file has timestamp dec 27 2011
>>>
>>> so it seem's that bootlogd doesn't work. Why not?
>>
>> I'm in the same situation that yours.
>>
>> AFAIK, the current implementation of bootlogd is broken, it does not
>> work though it did (sometimes) time ago.
>
> I solved the problem by installing bootlogd package.
not there, what the...? It may have been removed silently because I'm
sure I had it working and installed months ago.
Well, thanks, reinstalling again :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
Jun 29, 2012, 2:50:01 PM6/29/12
to
On 06/29/2012 09:58 AM, Camaleón wrote:
> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>
> I'm in the same situation that yours.
>
> AFAIK, the current implementation of bootlogd is broken, it does not work
> though it did (sometimes) time ago.
Strange... It is running here on 3 wheezy/sid partitions and also a sid
> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>
>> on my system I have enabled bootlogd: in /etc/default/bootlogd I have:
>> BOOTLOGD_ENABLE=Yes
>>
>> but the /var/log/boot
>>
>> file has timestamp dec 27 2011
>>
>> so it seem's that bootlogd doesn't work. Why not?
>
> I'm in the same situation that yours.
>
> AFAIK, the current implementation of bootlogd is broken, it does not work
> though it did (sometimes) time ago.
partition, without any problems.
WT
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
Jun 29, 2012, 3:10:04 PM6/29/12
to
On Fri, 29 Jun 2012 14:44:56 -0400, Wayne Topa wrote:
> On 06/29/2012 09:58 AM, Camaleón wrote:
>> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
(...)
> On 06/29/2012 09:58 AM, Camaleón wrote:
>> On Fri, 29 Jun 2012 04:53:53 +0200, Csanyi Pal wrote:
>>> so it seem's that bootlogd doesn't work. Why not?
>>
>> I'm in the same situation that yours.
>>
>> AFAIK, the current implementation of bootlogd is broken, it does not
>> work though it did (sometimes) time ago.
>
> Strange...
then.
> It is running here on 3 wheezy/sid partitions and also a sid
> partition, without any problems.
somehow removed from my system but it was not me who did it, at least not
on purpose.
And now I read that the config file is not needed any more or so it says
here:
***
http://wiki.debian.org/bootlogd
As from Wheezy, the bootlog package is automatically started as a daemon
in the normal way (with a sys-V like init.d script). No config file any
more.
***
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andrei POPESCU
Jun 29, 2012, 4:00:02 PM6/29/12
to
On Vi, 29 iun 12, 14:53:25, Camaleón wrote:
>
> Uh? This has been installed since... wait, you're right, the package is
> not there, what the...? It may have been removed silently because I'm
> sure I had it working and installed months ago.
That's probably when bootlogd was split in a dedicated package[1].
>
> Uh? This has been installed since... wait, you're right, the package is
> not there, what the...? It may have been removed silently because I'm
> sure I had it working and installed months ago.
Before that it was a functionality of initscripts.
[1] the changelog says 22.Dec.2012
Camaleón
Jun 30, 2012, 6:30:01 AM6/30/12
to
On Fri, 29 Jun 2012 22:49:46 +0300, Andrei POPESCU wrote:
> On Vi, 29 iun 12, 14:53:25, Camaleón wrote:
>>
>> Uh? This has been installed since... wait, you're right, the package is
>> not there, what the...? It may have been removed silently because I'm
>> sure I had it working and installed months ago.
>
> That's probably when bootlogd was split in a dedicated package[1].
> Before that it was a functionality of initscripts.
>
> [1] the changelog says 22.Dec.2012
Thanks. I see...:
> On Vi, 29 iun 12, 14:53:25, Camaleón wrote:
>>
>> Uh? This has been installed since... wait, you're right, the package is
>> not there, what the...? It may have been removed silently because I'm
>> sure I had it working and installed months ago.
>
> That's probably when bootlogd was split in a dedicated package[1].
> Before that it was a functionality of initscripts.
>
> [1] the changelog says 22.Dec.2012
http://packages.debian.org/changelogs/pool/main/s/sysvinit/sysvinit_2.88dsf-22.1/changelog#version2.88dsf-17
[ Josh Triplett ]
* Split bootlogd into a separate package. (Closes: #545181)
It would have been nice to have a notice displayed somewhere about the
removal of a binary or something that can indicate the users they need
to manually install the new stand-alone package if they wanted to keep
such funcionality.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages