Bug#588666: boot message stuck onto next message

2019-08-27 Thread Dmitry Bogatov
control: tags -1 +fixed-upstream [2019-08-26 16:32] Jesse Smith > On Sun, 25 Aug 2019 16:07:30 + Dmitry Bogatov wrote: > > > > > Each line a process sends: > > > > * should be prefixed by the name of the process that sent it. > > > > * should end with a newline. > > > > > > And (#398269)

Bug#588666: boot message stuck onto next message

2019-08-26 Thread Jesse Smith
On Sun, 25 Aug 2019 16:07:30 + Dmitry Bogatov wrote: > > > Each line a process sends: > > > * should be prefixed by the name of the process that sent it. > > > * should end with a newline. > > > > And (#398269) each line should be either from a process or the kernel, > > distinguishable

Bug#588666: boot message stuck onto next message

2019-08-25 Thread Dmitry Bogatov
control: reassign -1 startpar control: tags -1 upstream control: severity -1 wishlist [2019-08-22 21:31] Thorsten Glaser > > DB> Can you please elaborate what change to startpar you propose? I did not > > DB> understand. > > > > I think I am saying: > > > > Each line a process sends: > > *

Bug#588666: boot message stuck onto next message

2019-08-22 Thread Thorsten Glaser
On Fri, 23 Aug 2019, 積丹尼 Dan Jacobson wrote: > DB> Can you please elaborate what change to startpar you propose? I did not > DB> understand. > > I think I am saying: > > Each line a process sends: > * should be prefixed by the name of the process that sent it. > * should end with a newline.

Bug#588666: boot message stuck onto next message

2019-08-22 Thread 積丹尼 Dan Jacobson
DB> Can you please elaborate what change to startpar you propose? I did not DB> understand. I think I am saying: Each line a process sends: * should be prefixed by the name of the process that sent it. * should end with a newline.

Bug#588666: boot message stuck onto next message

2019-08-22 Thread Dmitry Bogatov
control: tags -1 +moreinfo [2010-07-11 18:45] jida...@jidanni.org > > "PR" == Petter Reinholdtsen writes: > PR> I guess smartmontools uses too long time, and thus startpar > PR> passes on incomplete lines causing such output. > > Perhaps make each line show who is doing the talking, > and

Bug#588666: boot message stuck onto next message

2010-07-11 Thread Petter Reinholdtsen
reassign 588666 sysvinit-utils thanks I don't understand the problem, as wicd and smartmontools both just seem to use the standard log_daemon_msg in /etc/init.d/* . This is probably caused by startpar, which have a limit on how long it wait for a line printed by the subprocesses to complete.

Bug#588666: boot message stuck onto next message

2010-07-11 Thread jidanni
PR == Petter Reinholdtsen p...@hungry.com writes: PR I guess smartmontools uses too long time, and thus startpar PR passes on incomplete lines causing such output. Perhaps make each line show who is doing the talking, and only one process allowed to print per line... That way it would be fine if

Bug#588666: boot message stuck onto next message

2010-07-10 Thread jidanni
X-debbugs-Cc: smartmonto...@packages.debian.org Package: initscripts Version: 2.88dsf-11 Severity: wishlist smartmontools is the only package that makes such mashed together ... # zgrep -nHi start.*start boot* boot:40:Sun Jul 11 06:26:35 2010: Starting S.M.A.R.T. daemon: smartdStarting Network