Your message dated Wed, 15 Nov 2006 17:42:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398783: messages from init scripts look awful with
upstart/consequence of paralelization
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Subject: messages from init scripts look awful with upstart/consequence of
paralelization
Package: upstart
Version: 0.2.7-1
Severity: minor
Hello,
I have installed upstart and I have seen that almost all "Starting ..."
messages are badly displayed, like below. I suspect the behaviour is due
to the paralel execution of the init scripts.
I think a solution would be to add a message interface as I suggested
previously to HMH in some private mails. See below the message I sent to
Henrique.
Starting foo ...
Starting bar services ...
- -----8<--------
Date: Thu, 3 Aug 2006 19:27:11 +0300
From: "Eddy Petrişor" <[EMAIL PROTECTED]>
To: "Henrique de Moraes Holschuh" <[EMAIL PROTECTED]>
Subject: New init scripts - a proposal
Hello Henrique,
I have watched some time ago your presentation wrt new init scripts. I
have a small proposal for a feature that would really help in
abstractisation of the used interface. Instead mandating to use echo
- -n "X is starting ..." then using "echo done.", I would suggest an
abstract set of message processors so tings like the following can be
done:
initmsg --start --long <service>
would print in a console "Starting <service>..."
initmsg --done service
would finish the message by printing "done"
initmsg --failed <service>
would print "failed."
and so on.
Under each command is what should the function do by default to be
equivalent to current policy. OTOH, this would allow:
- - nice progress bars and customised verbosity if splash screens are
used (text messages in a confined area, one text status line)
- - blinking icons or alike a-la-KDE or GNOME initialisation screen
- - nice [ok]/[fail]/[whatever] texts a-la-redhat/fedora
- - abstractisation of the message interface and possibility to do
something llike redirrecting only stderr into some error long without
messing with the display
- -----8<--------
- -- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (900, 'unstable'), (100, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-powerpc
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Versions of packages upstart depends on:
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
ii sysvinit-utils 2.86.ds1-34 System-V-like utilities
Versions of packages upstart recommends:
ii startup-tasks 0.2.7-1 definitions of essential tasks to
ii system-services 0.2.7-1 definitions of essential system se
ii upstart-compat-sysv 0.2.7-1 compatibility for System-V-like in
ii upstart-logd 0.2.7-1 boot logging daemon
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFWx3uY8Chqv3NRNoRAnQtAKC6pMpRLgBZXw45fuS3aPXBl9PkwQCfU2H5
CO2YZJV/opmAge75cgW/mQw=
=Kuyh
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 0.2.7-2
Eddy Petrișor wrote:
> Subject: messages from init scripts look awful with upstart/consequence of
> paralelization
> Package: upstart
> Version: 0.2.7-1
> Severity: minor
>
> Hello,
>
> I have installed upstart and I have seen that almost all "Starting ..."
> messages are badly displayed, like below. I suspect the behaviour is due
> to the paralel execution of the init scripts.
Hi Eddy,
the problem is not the parallel execution of the initscripts. Atm
upstart completely uses the initscripts from the old sysvinit package,
to boot the system. The problem is rather, that the getty on tty1 is
started as early as possible. This breaks the output of the initscripts.
This has been fixed in 0.2.7-2 (which has already been uploaded), where
logd does not output any messages at all anymore (it only logs to
/var/log/boot). This gives you the possibility to log in as early as
possible.
If you want the boot messages back, follow the instructions in
README.Debian (in 0.2.7-2).
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
