On 9/26/23 14:23, Laurent Bercot wrote:
>
> I agree with all you're saying here...
> ... except that this case makes no sense in the first place. A consumer
> and a non-consumer are fundamentally different things.
>
> A running service that is not a consumer does not read anything on its
>
On 5/28/22 12:15 PM, Dallin Dahl wrote:
> It turns out I had the same issue as Rio, since my login shell was still
> controlling my terminal. If I run:
>
> exec s6-setsid X :3 vt3
>
> while logged into tty3, I get an X display. However, I still can't
> seem to get it to work with s6-svscan.
On 5/22/22 10:07 AM, Guillermo wrote:
> Hello, Samuel.
>
> El sáb, 14 may 2022 a las 23:44, Samuel Holland escribió:
>>
>> X is started at boot from my user supervision tree[1], which is started by
>> the
>> user-* services in my system supervision tree[2].
>
On 5/13/22 10:47 PM, Guillermo wrote:
> Hello,
>
> El mié, 11 may 2022 a las 0:43, dallinjdahl escribió:
>>
>> I tried to run X under s6 with the following run file:
>>
>> ~~~
>> #!/usr/bin/execlineb
>> [...]
>> X :${screen} vt${screen}
>> ~~~
>> [...]
>> (WW) xf86OpenConsole: VT_ACTIVATE failed:
On 9/5/20 3:26 PM, Rio Liu wrote:
>>
>> Well the catch-all logger is supposed to be just that: a catch-all
>> logger. That means that ideally, every service should have its own
>> dedicated logger, typically writing to /var/log/something, and the
>> catch-all logger is only used for exceptional
On 12/2/19 3:32 PM, Laurent Bercot wrote:
>> As a guy who has both daemontools and s6 installed on the same box, I
>> thank you from the bottom of my heart for:
>>
>> 1) Prepending s6- to each command so they don't clash with djb's
>> 2) Except for the s6-, naming them the same as djb's so I have
On 8/18/19 1:26 AM, Laurent Bercot wrote:
>> Sorry if I read this thread too hastily, but why not just keep /proc etc
>> mounted, as was seemingly the way with s6-linux-init <=v0.4.x.x (and
>> therefore slew)? Since the asymmetry is by nature, simply respecting it
>> appears to be one minimalist
