On 8/9/21 7:06 PM, Javier wrote:
> But to make sure on "s6-setuidgid" usage [1], I can just use it as
> "exec" for example, like using:
>
>> s6-setuidgid <owner>:<primary_group> <cmd> <cmd_args>
>
> Instead of:
>
>> exec <cmd> <cmd_args>
>
> Where <cmd> is an actual executable...
You still would need exec. It would instead be:
s6-setuidgid <uid:gid> exec <cmd> <args>
> @dudemanguy, do you happen to know if the systemd root launching as user
> feature (not the user launch upon login, which can easily be achieved
> with a shell profile) is to come to s6? Or runit for that matter?
> Like: "/etc/systemd/system/<service>@.service" on systemd? Those
> services don't require user login, and are pretty handy if calling
> screen from a root service doesn't work for example...
If you mean manage services as purely a non-root user (s6-rc commands)
and such, it's possible. You would need to set it up yourself, but
basically it would be running a s6-svscan process as a local user and
then running an s6-rc-init using the directories created by that
s6-svscan process. I don't think doing this would solve your problem
though.
> Ohh well, I guess the need to be actually "logged in" might come from
> logind, which is becoming really a pain for several use cases of mine,
> :( I guess there's no way to get artix working without elogind, since
> it's so basic for artix, :(.
I don't think this is logind related. I would expect the same issue
everywhere. I'm no expert on screen at all so perhaps I am wrong, but I
personally would not think it would work without an actual shell active
and running (i.e. you are logged in).
More information about the artix-general
mailing list