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 agains
On Fri, 28 Oct 2011 13:30:18 +0100, Bob Brewer 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
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
>> sysvi
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).
>>>
>>> T
Camaleón wrote:
>> 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" parti
boot logging.
>>
>> (...)
>>
>> Mmm... are the kernel logs being written okay? Have you a separated "/
>> var" partition?
>
> No problem with kern.log or apparently any log file in /var/log. I do
> have /var on a separate partition, may-be there is a
Camaleón wrote:
> Mmm... then try to direct bootlogd logs to the root partition and see
> what happens. This could be done by passing "-l" argument and I
> suppose you will have to tweak the "/etc/init.d/bootlogd" script file
> :-?
>
I tried adding "-l /bo
On Sat, 29 Oct 2011 16:54:05 +0100, Bob Brewer wrote:
> Camaleón wrote:
>
>> Mmm... then try to direct bootlogd logs to the root partition and see
>> what happens. This could be done by passing "-l" argument and I suppose
>> you will have to tweak the
Camaleón wrote:
> It works here but I edited this line:
>
> BOOTLOGD_OPTS="-r -c -l /bootlog"
I've now changed mine to be the same as yours
>
> After restarting the system the file is indeed placed at the "/"
> instead "/var/log/boot".
I
he system the file is indeed placed at the "/"
>> instead "/var/log/boot".
>
> If I now run /etc/init.d/bootlogd start It does indeed write an empty
> log file /bootlog and on shutting down writes some 'stopping' entries
> into the file.
So the service ca
em first started. This PC is nearly 10 years old and its
config hasn't been changed since the problem first started, so I think I
should be able to rule out a hardware related issue.
I have now had a look at /etc/rc2.d and see that bootlogd isn't started
by sysvinit-utils and o
problem :-)
>
> Unfortunately my logs don't go back far enough to see what was changed
> when the problem first started. This PC is nearly 10 years old and its
> config hasn't been changed since the problem first started, so I think I
> should be able to rule out a hardwar
; but it is enabled by default and both
> (kernel and booting services messages) fall here, in the same file.
>
I first started running Woody Debian and Red Hat before that and can
only remember logging to /var/log/boot. I don't remember problems before
now though.
>> If I add a link to b
So, based on another email "logging all output at boot"
I decided to update sysvinit and it's dependencies so
that I could view the output in boot.log. I just upgraded
sysvinit from Unstable this morning.
I installed and went to /etc/defaults/bootlogd
and changed to =Y
I still do
I need to know what starts bootlogd. My default runlevel is 2 and in
rc2.d there is S99stop-bootlogd but nothing else. I'm having a
problem since I upgraded from sarge (where everything was fine) to
etch in November that less than 25% of the boot messages actually
appear in /var/log
I've read in internet about bugs and problems in the past with that package,
but no solution good for me. I installed bootlogd, rebooted, but the file
/var/log/boot, the one supposed to store bootlogd reports, still says:
(Nothing has been logged yet.)
Please help.
Thanks,
Rodolfo
-
s morning.
>
> I installed and went to /etc/defaults/bootlogd
> and changed to =Y
>
> I still do not get a /var/log/boot.log
> and I see a quick message during boot
>
> bootlogd ??.?? Bad File Descriptor
disk error? Try reinstalling? (It Worked For Me so I'm just
On Sunday, April 26, 2015 at 4:20:04 AM UTC+5:30, Rodolfo Medina wrote:
> I've read in internet about bugs and problems in the past with that package,
> but no solution good for me. I installed bootlogd, rebooted, but the file
> /var/log/boot, the one supposed to store bootlogd
Rusi Mody writes:
> On Sunday, April 26, 2015 at 4:20:04 AM UTC+5:30, Rodolfo Medina wrote:
>> I've read in internet about bugs and problems in the past with that package,
>> but no solution good for me. I installed bootlogd, rebooted, but the file
>> /var/log/boot,
Quoting Rusi Mody (rustompm...@gmail.com):
> On Sunday, April 26, 2015 at 4:20:04 AM UTC+5:30, Rodolfo Medina wrote:
> > I've read in internet about bugs and problems in the past with that package,
> > but no solution good for me. I installed bootlogd, rebooted, but the fi
Am 26.04.2015 um 18:40 schrieb David Wright:
> Does anyone know how to disable clearing? (I've had --noclear in
> /etc/inittab for years but that ceased working with jessie.)
https://wiki.archlinux.org/index.php/Disable_clearing_of_boot_messages
--
Why is it that all of the instruments seeking
Hi list,
It seems that my dmesg and bootlogd log sizes are not big enough. This
is at least what I suspect, since not everything is logged in
/var/log/dmesg and /var/log/boot, but only the last lines. So does
anybody know if it's possible to increase the maximum log sizes
somewhere? And
On 08/12/2006 07:23 PM, Rico Hauke wrote:
Hi list,
It seems that my dmesg and bootlogd log sizes are not big enough. This
is at least what I suspect, since not everything is logged in
/var/log/dmesg and /var/log/boot, but only the last lines. So does
anybody know if it's possible to inc
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-user-requ...@lists.
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
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 d
Dom 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 th
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. W
Camaleón 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
>>
>
On Fri, 29 Jun 2012 16:44:12 +0200, Csanyi Pal wrote:
> Camaleón 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
>>>
>>
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 wor
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:
(...)
>>> so it seem's that bootlogd doesn't work. Why not?
>>
>> I'm in the same s
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 w
; 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...:
http://packages.debian.org/change
In article <[EMAIL PROTECTED]>,
Niels L. Ellegaard <[EMAIL PROTECTED]> wrote:
>I just looked at my system (Sarge/sid/linux-image-2.6.5-386), and it
>seems that my bootlogd is not running. It does not create a
>/var/log/bootlogd and at some point during the boot process I get
After upgarding bootlogd and initscripts 2.88dsf-42 -> 2.88dsf-43,
and other packages that are built from sysvinit, I found that
1. /etc/init.d/bootlogd
2. /etc/init.d/stop-bootlogd
3. /etc/init.d/stop-bootlogd-single
are no longer installed. Looks similar to
http://bugs.debian.
I did not have them, just a "bootlogd.dpkg-bak".
A purge then reinstall of "bootlogd" fixed that for me.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Ar
Dear Gurus,
Hi i have a script in /etc/init.d/ctnscript
with a symlink
in
/etc/rc2.d/S99ctnscript
when i tried to install gpm then i got a series of errors
insserv: Starting ctnscript depends on stop-bootlogd and therefore on system
facility `$all' which can not be true!
repeated
Mitchell Laks wrote:
Dear Gurus,
Hi i have a script in /etc/init.d/ctnscript
with a symlink
in
/etc/rc2.d/S99ctnscript
when i tried to install gpm then i got a series of errors
insserv: Starting ctnscript depends on stop-bootlogd and therefore on system
facility `$all' which can n
On Wed, Jul 28, 2010 at 9:49 AM, hugo vanwoerkom wrote:
> Mitchell Laks wrote:
>> Hi i have a script in /etc/init.d/ctnscript
>> with a symlink
>> in /etc/rc2.d/S99ctnscript
>> when i tried to install gpm then i got a series of errors
>> insserv: Starting ctnsc
40 matches
Mail list logo
