Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #206687 > unrolled thread
| Started by | "Steve Keller" <keller.steve@gmx.de> |
|---|---|
| First post | 2019-03-27 19:50 +0100 |
| Last post | 2019-06-05 21:10 +0200 |
| Articles | 4 — 4 participants |
Back to article view | Back to linux.debian.user
Sequential boot with systemd? "Steve Keller" <keller.steve@gmx.de> - 2019-03-27 19:50 +0100
Re: Sequential boot with system d? Brian <ad44@cityscape.co.uk> - 2019-03-27 21:20 +0100
Re: Sequential boot with systemd? Darac Marjal <mailinglist@darac.org.uk> - 2019-03-27 22:20 +0100
Re: Sequential boot with systemd? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-05 21:10 +0200
| From | "Steve Keller" <keller.steve@gmx.de> |
|---|---|
| Date | 2019-03-27 19:50 +0100 |
| Subject | Sequential boot with systemd? |
| Message-ID | <xGlMB-3zY-1@gated-at.bofh.it> |
Is it possible to configure systemd to *not* start services in parallel? I'd prefer deterministic boot with readable boot messages. With parallel start, messages of different services get intermingled and it's much more difficult to identify possible problems. Steve
[toc] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2019-03-27 21:20 +0100 |
| Subject | Re: Sequential boot with system d? |
| Message-ID | <xGnbH-4zv-5@gated-at.bofh.it> |
| In reply to | #206687 |
On Wed 27 Mar 2019 at 19:27:21 +0100, Steve Keller wrote: > Is it possible to configure systemd to *not* start services in > parallel? I'd prefer deterministic boot with readable boot > messages. With parallel start, messages of different services get > intermingled and it's much more difficult to identify possible > problems. Would Requires plus After get you going? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Date | 2019-03-27 22:20 +0100 |
| Message-ID | <xGo7M-5ck-3@gated-at.bofh.it> |
| In reply to | #206687 |
On 27/03/2019 18:27, Steve Keller wrote: > Is it possible to configure systemd to *not* start services in > parallel? I'd prefer deterministic boot with readable boot > messages. With parallel start, messages of different services get > intermingled and it's much more difficult to identify possible > problems. > > Steve > Have you thought about installing plymouth? Most people know it for it's "splash screen" capabilities, but it also acts as a boot message manager. You may find that installing plymouth and using the "text" or "details" themes clears up your messages.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2019-06-05 21:10 +0200 |
| Message-ID | <y5Jsl-Q0-3@gated-at.bofh.it> |
| In reply to | #206687 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 27 mar 19, 19:27:21, Steve Keller wrote: > Is it possible to configure systemd to *not* start services in > parallel? That would be very difficult to achieve with systemd, your best option would probably be to switch to sysv. > I'd prefer deterministic boot with readable boot > messages. With parallel start, messages of different services get > intermingled and it's much more difficult to identify possible > problems. Not an option for boot messages, but journalctl has some advanced filtering options that one can use, e.g. '-b -u ssh' will show only the messages from the current boot and from units matching the pattern 'ssh'. If you only care about possible problems -p (priority) could also be useful. It shouldn't be very difficult to script something based on that. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web