supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
* Linking s6-linux-init to s6-supervise
@ 2025-01-28 22:34 Ian Macdonald via supervision
  2025-01-29  1:53 ` Laurent Bercot
  0 siblings, 1 reply; 3+ messages in thread
From: Ian Macdonald via supervision @ 2025-01-28 22:34 UTC (permalink / raw)
  To: supervision

Hi,

I have been experimenting with s6* programs for a couple of months and,
by progressively replacing the sysv boot scripts with s6 services, now
have my current system booting and running without sysvinit. Supervised
logging with s6-log is also working, replacing sysklogd.

Despite not really knowing how all this worked, I decided to build a
new version of Linux From Scratch (LFS) without sysvinit and sysklogd,
using s6* instead. S6LFS?

The new build boots, I get a Login prompt and s6-svscan is running as
pid 1 but nothing else happens. None of the 'compiled' services are
copied to the /run directory.

I have clearly missed a step, hopefully a simple one, and the annoying
thing is that I obviously took that step for my current working system
without recognising it!

Any help would be appreciated.

Thanks 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Linking s6-linux-init to s6-supervise
  2025-01-28 22:34 Linking s6-linux-init to s6-supervise Ian Macdonald via supervision
@ 2025-01-29  1:53 ` Laurent Bercot
  2025-01-29 22:29   ` Ian Macdonald via supervision
  0 siblings, 1 reply; 3+ messages in thread
From: Laurent Bercot @ 2025-01-29  1:53 UTC (permalink / raw)
  To: supervision

>The new build boots, I get a Login prompt and s6-svscan is running as
>pid 1 but nothing else happens. None of the 'compiled' services are
>copied to the /run directory.
>
>I have clearly missed a step, hopefully a simple one, and the annoying
>thing is that I obviously took that step for my current working system
>without recognising it!

  Wild guess: have you edited your /etc/rc.init to uncomment the
s6-rc-init and s6-rc invocations?

--
  Laurent


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Linking s6-linux-init to s6-supervise
  2025-01-29  1:53 ` Laurent Bercot
@ 2025-01-29 22:29   ` Ian Macdonald via supervision
  0 siblings, 0 replies; 3+ messages in thread
From: Ian Macdonald via supervision @ 2025-01-29 22:29 UTC (permalink / raw)
  To: supervision; +Cc: Laurent Bercot

On Wed, 29 Jan 2025 01:53:05 +0000
"Laurent Bercot" <ska-supervision@skarnet.org> wrote:

> >The new build boots, I get a Login prompt and s6-svscan is running as
> >pid 1 but nothing else happens. None of the 'compiled' services are
> >copied to the /run directory.
> >
> >I have clearly missed a step, hopefully a simple one, and the
> >annoying thing is that I obviously took that step for my current
> >working system without recognising it!
> 
>   Wild guess: have you edited your /etc/rc.init to uncomment the
> s6-rc-init and s6-rc invocations?
> 
> --
>   Laurent
> 

Good guess.

Uncommenting the s6 invocations still left me at Login prompt but
running
	s6-rc -u change default
now brings up the system. This exposed a problem with an unknown user
(s6log) which I had forgotten to add to the new build.

It's early days; I think I'll clean out /etc/s6* and start again.

Thanks for your help.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-01-29 22:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-28 22:34 Linking s6-linux-init to s6-supervise Ian Macdonald via supervision
2025-01-29  1:53 ` Laurent Bercot
2025-01-29 22:29   ` Ian Macdonald via supervision

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).