Thanks for the update. There should be enough information here for a
developer to see where the problem is, so I'm going to mark this as
Triaged and let them handle it from here.
** Changed in: sysvinit (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- bootlogd not working (sysv
Hi all,
Doing it on a friend's lappy. Its on jaunty and even after doing the
changes required in /etc/default/booglogd , shutting down the system
and restarting it don't have anything except the same message 'Nothing
has been logged in yet' in /var/log/boot
--
Regards,
Shiris
Ok, so no fixes for this have been backported. Note: backports are
*usually* ok for normal desktop users, I wouldn't advise it for a server
install, but a lot of things that work in later versions are pulled
back. I am marking this as Low and Confirming it.
** Changed in: sysvinit (Ubuntu)
Impo
** Summary changed:
- bootlogd not working (sysvinit)
+ bootlogd not working (sysvinit) - nothing has been logged yet
** Description changed:
Binary package hint: sysvinit
i tried to set up the boot logging on feisty
first i enabled in the file : /etc/default/bootlogd (no-->yes)
Well, Teej,
I've tested it on my Hardy as you suggested after enabling backports and
making a full update with it. No changes.
I mean after setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and
setting bottlogd to be started at boot time nothing was logged on my
machine.
The only thing I can
Of course not. The reason we ask this is that the problem may be fixed
in a later version, and the fixes may be able to be backported into
previous versions, i.e. Hardy, Intrepid, etc. Do you already have
backports enabled? If not, can you try enabling it in Software Sources
and updating everything
Teej, does your message mean that these of us who runs Ubuntu 8.04 LTS
would stay on cold until the next LTS release? Or are you going to
update us as well?
These is a long expected feature. And no changes so far. :-(
Thanks.
--
bootlogd not working (sysvinit)
https://bugs.launchpad.net/bugs/
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed in
Hi, Pev.
I've seen you already placed this "nice" suggestion here:
https://bugs.launchpad.net/upstart/+bug/98955
Apparently you did it without bothering reading full discussion. The
problem with your suggestion is that neither Feisty nor Hardy users
cannot install sysvinit. There is a known pa
Well, a bit late, but:
in script which is suppose to start logging daemon is
DAEMON=/sbin/bootlogd
[ -x "$DAEMON" ] || exit 0
So you have to install a package which have file 'sbin/bootlogd'. So run
command
apt-get install sysvinit
Pev
--
bootlogd not working (sysvinit)
https://bugs.launchpa
10 matches
Mail list logo
