Re: `bootlogd' not working

2015-04-26 Thread Michael Biebl
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

Re: `bootlogd' not working

2015-04-26 Thread David Wright
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 file > > /var/log/boot, the

Re: `bootlogd' not working

2015-04-26 Thread Rodolfo Medina
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, the one supposed to store boo

Re: `bootlogd' not working

2015-04-25 Thread Rusi Mody
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 reports, still says

Re: bootlogd

2011-10-31 Thread Bob Brewer
Calamine wrote: > On Mon, 31 Oct 2011 10:46:55 +, Bob Brewer wrote: > >> Calamine wrote: >> >>> Yes, and that sounds even weirder, I mean, that can be launched on a >>> running system but fails when loading. I've also found another bug >>> report (which is older than the one you pointed befo

Re: bootlogd

2011-10-31 Thread Camaleón
On Mon, 31 Oct 2011 10:46:55 +, Bob Brewer wrote: > Camaleón wrote: > >> Yes, and that sounds even weirder, I mean, that can be launched on a >> running system but fails when loading. I've also found another bug >> report (which is older than the one you pointed before) that basically >> come

Re: bootlogd

2011-10-31 Thread Bob Brewer
Camaleón wrote: > Yes, and that sounds even weirder, I mean, that can be launched on a > running system but fails when loading. I've also found another bug > report (which is older than the one you pointed before) that basically > comes to say the same as you: > > http://bugs.debian.org/cgi-bin/b

Re: bootlogd

2011-10-29 Thread Camaleón
On Sat, 29 Oct 2011 19:00:55 +0100, Bob Brewer wrote: > 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

Re: bootlogd

2011-10-29 Thread Bob Brewer
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". If I now run /etc/init.d/bootlogd start It does indeed w

Re: bootlogd

2011-10-29 Thread Camaleón
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 "/etc/init.d/bootlogd" script file :-? >> >

Re: bootlogd

2011-10-29 Thread Bob Brewer
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 /bootlog" to the DAEMON=/sbin/bootlogd line

Re: bootlogd

2011-10-29 Thread Camaleón
On Sat, 29 Oct 2011 13:00:12 +0100, Bob Brewer wrote: > 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 ke

Re: bootlogd

2011-10-29 Thread Bob Brewer
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

Re: bootlogd

2011-10-29 Thread Camaleón
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 a

Re: bootlogd

2011-10-28 Thread Bob Brewer
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 bee

Re: bootlogd

2011-10-28 Thread Camaleón
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 > sysvinit-utils pack

Re: bootlogd: ioctl (/dev/ttyzf, TIOCCONS): Bad file descriptor

2004-05-03 Thread Miquel van Smoorenburg
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 the >following error. >