[2019-08-27 16:35] Jan Braun
> > > Personally, I'd prefer linking /etc/sv/foo/supervise to a place of my
> > > choosing and expect that link to be preserved. Not sure how others
> > > would feel, or how they'd try to deal with the issue.
> >
> > Why would you need it? Content of 'supervise'
Hi,
Dmitry Bogatov schrob:
> [2019-08-24 16:03] Jan Braun
> > That means they'll get a conffile prompt if/whe the maintainer changes
> > the run file.
>
> This can be solved in /lib/runit/invoke-run. Something like running
> /etc/service/foo/run.pre before "run".
>
> Feel free to file
[2019-08-24 16:03] Jan Braun
> Dmitry Bogatov schrob:
> > No, I did not consider this aspect. Thank you.
> > But since runscripts are conffiles, admin can add line
> >
> > chown -R trusted_user:0 /run/runit/supervise/foo
> >
> > into /etc/sv/foo/run, and they will be preserved during
Dmitry Bogatov schrob:
> No, I did not consider this aspect. Thank you.
> But since runscripts are conffiles, admin can add line
>
> chown -R trusted_user:0 /run/runit/supervise/foo
>
> into /etc/sv/foo/run, and they will be preserved during upgrade. Not
> that staightforward, but still
Il giorno ven 23 ago 2019 alle ore 13:22 Dmitry Bogatov
ha scritto:
> [...]What about making
> in postinst symlink
>
>/run/runit/supervise/foo -> /lib/runit/supervise/foo
>
> if latter exists? It should resolve problem with overwriting symlink of
> running process.
It's ok for me,
[2019-08-21 16:56] Lorenz
> >>if test ! -h "$svdir"/supervise; then
> >> rm -rf "$svdir"/supervise
> >> -ln -s /var/lib/runit/supervise/"$sv" "$svdir"/supervise
> >> +ln -s /run/runit/supervise/"$sv" "$svdir"/supervise
> >
> >Will it handle both /var/lib and
[2019-08-21 18:46] Jan Braun
> Source: dh-runit
> Followup-For: Bug #934500
>
> Dear Maintainer,
> I'd like to point out that moving the supervise directories to /run
> means that they get wiped on reboot. Therefore the local admin can't
> persistently change their permissions, to give certain
Source: dh-runit
Followup-For: Bug #934500
Dear Maintainer,
I'd like to point out that moving the supervise directories to /run
means that they get wiped on reboot. Therefore the local admin can't
persistently change their permissions, to give certain users additional
rights.
Personally, I see
>>if test ! -h "$svdir"/supervise; then
>> rm -rf "$svdir"/supervise
>> -ln -s /var/lib/runit/supervise/"$sv" "$svdir"/supervise
>> +ln -s /run/runit/supervise/"$sv" "$svdir"/supervise
>
>Will it handle both /var/lib and /run/runit location?
Mmm.. No
In my system
control: tags -1 +patch
[2019-08-19 15:21] Lorenzo Puliti
> Package: dh-runit
> Version: 2.8.13.2
> Followup-For: Bug #934500
>
> The patch for 'update-service' is attached
>
>
> From 200a8e68089a30177798e1e5f5e6c6def45fef64 Mon Sep 17 00:00:00 2001
> From: Lorenzo Puliti
> Date: Mon, 19 Aug
Package: dh-runit
Version: 2.8.13.2
Followup-For: Bug #934500
The patch for 'update-service' is attached
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.20.3-van (SMP
[2019-08-16 23:22] Lorenz
>
> part 2 text/plain 323
> Il giorno mer 14 ago 2019 alle ore 21:22 Dmitry Bogatov
> ha scritto:
>
> >Yes, I go this way.
>
> Ok.
> in commit d07519ae you already create /run/runit/supervise directory,
> but the directory for the appendant log of
Il giorno mer 14 ago 2019 alle ore 21:22 Dmitry Bogatov
ha scritto:
>Yes, I go this way.
Ok.
in commit d07519ae you already create /run/runit/supervise directory,
but the directory for the appendant log of 'foo' service will be
/run/runit/log/supervise/foo
or
/run/runit/supervise/foo.log ?
[2019-08-12 10:10] Lorenz
> [...]
> I don't see a strong reason to have persistent supervise directories: the
> files inside are mostly (if not all) not recyclable, bug like #919296
> proves that pre-create files with the porpose of speeding up the start of a
> runsv process doesn't work.
>
Il giorno dom 11 ago 2019 alle ore 19:48 Dmitry Bogatov
ha scritto:
> The simpliest fix is revert of #924903. More attractive way is to move
> supervise directories into /run.
The permission issue is not essential to me, but i prefer to move supervise
directories into /run.
I don't see a strong
Package: dh-runit
Version: 2.8.13.2
Severity: normal
In #924903 permissions of /var/lib/runit/supervise were changed from 755
to 700. As pointed by latest Lintian version, Policy 10.9 recommends
755.
The simpliest fix is revert of #924903. More attractive way is to move
supervise directories
16 matches
Mail list logo
