Thanks Laurent for the brief detail. That really helps.
I have checked the Private_Dirty memory in "smaps" of a s6-supervise
process and I don't see any consuming above 8kB. Just posting it here
for reference.
grep Private_Dirty /proc/991/smaps
Private_Dirty: 0 kB
Private_Dirty:
Dewayne,
Thanks for the details. We already have such an implementation (multiple
producers with one consumer) but still our s6-log instances are high. Many
of our services require direct logger services. We can reduce the direct
logger services by creating a funnel and using regex to separate the
Hi Team,
I would like to hear from you for a few queries. Please help.
1. Why do we need to have separate supervisors for producer and consumer
long run services? Is it possible to have one supervisor for both producer
and consumer, because anyhow the consumer service need not to
Thanks Laurent and Colin for the suggestions. I will try to build a fully
static s6 with musl toolchain. Thanks for the detailed analysis
once again.
--
Arjun
On Wed, Jun 9, 2021 at 5:18 PM Laurent Bercot
wrote:
> >I have checked the Private_Dirty memory in "smaps" of a s6-supervise
> >process
Hi Team,
I am facing an issue at the moment of shutting down the system. Whenever I
reboot the system, it is triggering "s6-rc -v2 -bda change" and stops all
the services. But one service is not responding and it hangs. This blocks
the reboot.
ps -aef | grep s6-rc
root 2770 2707 0 08:24 ?
Hi Team,
We are trying to migrate from systemd init system to S6. We have a few
queries, please help us on the same.
1. In systemd, the services are grouped as targets and each target depends
on another target as well. They start as targets. [ex: Reached
local-fs.target, Reached network.target,
Thanks Laurent for the detailed explanations. We did a bootup speed
comparison between S6 and systemd. S6 is able to boot up slightly faster
than systemd. Actual result is 4-4.5% faster but we were expecting
something near to 20%.
Ours is a bit complex setup with more than 140 services (includes a
