Re: Dependencies are not automatically activated with `set enable`; is that correct?

From: <lumaro_at_disroot.org>
Date: Wed, 21 Oct 2026 22:32:05 +0200

El 2026-10-21 22:13, Brett Neumeier via supervision escribió:

> On 10/21/26 11:30, lumaro.disroot.org via supervision wrote:
>
>> When I activate libvirtd, this message appears.
>> _ $ doas s6 enable libvirtd _
>> _s6-rc-set-change: warning: the following services (dependencies of
>> the ones given as arguments, or part of the same pipeline) also need
>> to be changed to "active": virtlogd-srv virtlogd-log virtlockd-srv
>> virtlockd-log _
>>
>> So, is this the correct way?
>> _ $ doas s6 enable virtlogd virtlockd libvirtd_
>
> You could simply add the "-I pull" argument so that dependencies are
> pulled in -- e.g.
>
> $ doas s6 enable -I pull libvirtd
>
> That's what I do, and it seems to work well.

Nice, thanks Brett, its works !

I tried with "-p --pull-dependencies apply the rx change to unlisted
dependencies as well" and works too.

  $ doas s6 set enable -p libvirtd
s6-rc-set-change: info: the following services (dependencies of the ones
given as arguments, or part of the same pipeline) are also being changed
to "active": virtlogd-srv virtlogd-log virtlockd-srv virtlockd-log
s6-rc-set-change: info: service libvirtd-srv already existed in rxset
active of set current in repository /etc/s6/repo
s6-rc-set-change: info: service libvirtd-log already existed in rxset
active of set current in repository /etc/s6/repo

...
libvirtd-srv active
libvirtd-log active
virtlogd-srv active
virtlogd-log active
virtlockd-srv active
virtlockd-log active
---
How did I not see this option before? X-x
I'm sharing this tip, feel free to check it out. Thanks, Luis.
Received on Wed Oct 21 2026 - 22:32:05 CEST

This archive was generated by hypermail 2.4.0 : Wed Oct 21 2026 - 22:32:45 CEST