have. Is there a statement from systemd
maintainers that says that they have give up with the standalone
package, maybe some IRC chat or it's just your sixth sense?
Lorenzo
s: #981683)
+ Many thanks to Helmut Grohne
Regards,
--
Lorenzo Puliti
o "preinst" instead of "postinst"?
I can think about this, but i likely need a discussion on
Debian Devel first.
Anyway this can happen only after Bullseye release, or maybe in
experimental, but not right now.
> Cheers,
> Lars
Regards,
Lorenzo
Package: sysuser-helper
Version: 1.3.5
Severity: important
X-Debbugs-Cc: plore...@disroot.org
Note for myself: after recent TC decision Debian is going to support merged-usr
only,
starting from Bookworm.
Sysuser-helper ships files under /lib/sysuser-helper/ so need a transition plan.
-- System
On Fri, 05 Feb 2021 10:16:14 +0100
Lorenzo Puliti wrote:
> Package: dh-sysuser
> Version: 1.3.5
> Severity: wishlist
> X-Debbugs-Cc: plore...@disroot.org
>
> Note: CC Helmut Grohne as he started the discussion,
> CC Niels Thykier as he might want to say something he
not sure what can
be the advantage of one approach versus the other.
I plan to keep this bug open for the next release cycle so there is time
for people to highlight bug or other problems with this package.
Regards,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unsta
On Wed, 3 Feb 2021 09:15:48 +0100
Helmut Grohne wrote:
> On Tue, Feb 02, 2021 at 11:47:41PM +0100, Lorenzo wrote:
> > thanks for the patch. I guess that it is because this package use
> > only perl ans shell, am I correct?
>
> Not exactly. Multi-Arch is an assertion of how
Package: dh-sysuser
Version: 1.3.5
Severity: normal
X-Debbugs-Cc: plore...@disroot.org
Helmut Grohne in #981683
> Further development seems like a good idea. [...]
> As far as I can tell,project consensus is that system users
> should not be removed on purge, but dh-sysuser does so.
Reminder f
Package: dh-sysuser
Version: 1.3.5
Severity: normal
X-Debbugs-Cc: plore...@disroot.org
Helmut Grohne, from #981683
> Further development seems like a good idea. The package uses useradd
> instead of the policy-recommended adduser. Is there a good reason for
> doing so?
Reminder for myself:
Chec
n logging in on tty.
Thanks for spotting this, I don't use session tracking on VT so I wasn't
aware of this problem.
> Please consider changing package 'getty-run' to merely suggest fgetty
> instead of recommending it.
I need to think about for a while, but it s
ck with something that does not need to go through a compiler,
like sh perl or python, it's always safe to mark Multi-Arch ?
Regards,
Lorenzo
til
Bullseye is released. If you think this bug still affects runit-run then
please follow up here so i can clone this bug and fix it in unstable.
Best Regards,
Lorenzo
yright for systemd manpages
Regards,
--
Lorenzo Puliti
s
Regards,
--
Lorenzo Puliti
or now, but that is
> also inconsistent since the main supervise symlink is taken care of by
> dh_runit.
>
> The right logic I think would be to make the symlink is logscript is
> not given but a log/run script is present.
>
> Cheers,
>
Hi Mathieu,
Thanks for the report, will fix this in 2.10.3.
Cheers,
Lorenzo
to 2.10.3
* Bump Stadards-Version to 4.5.1
Regards,
--
Lorenzo Puliti
o QA Group (see #975378)
* Bump debhelper-compat to 13
* Bump Standards-Version to 4.5.1
* d/clean: remove autogenereted manpages
* Provide systemd-sysusers
* Set Rules-requires-root to no
* Enable the standard Salsa CI pipeline
Regards,
--
Lorenzo Puliti
the sysadmin will be able to delete the symlinks (or set an
arbitrary boot order) without having to deal with insserv reordering
the links. It also ensures that the service does not get
started/stopped automatically with package upgrades.
Thorsten, could you please clarify which approach you think will better
suits your needs?
Lorenzo
file for runit-init
Regards,
--
Lorenzo Puliti
ice, to be broken, that is, stopped.
>
> I just had this happen, so it isn’t an academic mind exercise.
>
> bye,
> //mirabilos
I suspect what you want is a new feature in update-rc.d, but it depends
on your answer to my question above.
Lorenzo
ory, the code
that you are looking for will be written by dh-installinit in place of
the #DEBHEPLER# placeholder, during the build of the package.
To find out what the postinst will look like just compare the one in the
source with the one in the deb package in the archive.
Lorenzo
d
* Set maintainer to QA Group (see #947640)
.
[ Lorenzo Puliti ]
* Bump SV to 4.5.1, no changes required
* d/control: Add shlibs:Depends (Closes: #969063)
+ Thanks to Aurelien Jarno
* Cleanup unused lintian overrides
Regards,
--
Lorenzo Puliti
package with
> "systemd" in the name (even though it shouldn't depend on systemd)
> which is going to cause confusion. The maintainer community will
> hopefully have better advice that results in a cleaner transition.
Thanks for the suggestion, i'll see what I can do
Lorenzo
complain that i broke their
setup with an unnecessary change..
I think I will leave this bug open for a while (for reference to other
users that may
run into the same issue) but unfixed, as I don't have an idea for a fix
that does not have the
potential to break other people's stuff.
I'm still open to suggestions and further discussion
Lorenzo
What does 'systemctl status runit.service' say? (note the second line
'vendor preset: enabled')
Regards,
Lorenzo
Debhelper Compat to 13
- Disable openstack-pkg-tools ( see #976038)
* Bump S-V to 4.5.1
* Set Maintainer to QA Group (see #975377)
* Set Rules-requires-root to no
Regards,
--
Lorenzo Puliti
-buildpackage: info: source version 0.2+2019.05.21.git.44a55796ba-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Lorenzo Puliti
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
fakeroot debian/rules clean
end of the forced-rescan-test
* Fix some minor lintian tag
* Bump dh compat level to 13
* d/rules: fix broken autopkgtest phony target
* d/runit.NEWS: document recent changes
* Do not restart the gettys on upgrade
* Suggests socklog with runit
* Release to unstable
Regards,
--
Uploaded again, since with the previous one i forgot to bump dh-runit
version.
Regards,
Lorenzo
On 11/16/20 1:32 AM, Lorenzo Puliti wrote:
> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-Cc: plore...@disroot.org
>
> Dear mentors,
>
> I am looking for a spons
le.
Please be patient until the package finds a sponsor.
Regards,
Lorenzo
Git repo:
https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/tree/2.10.2-release
Changes since the last upload:
dh-runit (2.10.2) unstable; urgency=medium
.
* Don't run shake autopkgtest on armhf and armel (Closes: #973337)
* Allow outptut to stderr for update-rc.d test
Regard
etc/elogind/logind.conf:14: Unknown section 'Login'. Ignoring.
/etc/elogind/logind.conf:38: Unknown section 'Sleep'. Ignoring.
Not sure if it's really ignoring the conf file or what..
Thanks for your work,
Lorenzo
properly declare
the autopkgtest non compatible with armel and armhf, so that it will be auto
skipped :/
Regards,
Lorenzo
Thank You :)
On 10/29/20 7:24 PM, Thomas Liske wrote:
> Hi Lorenzo,
>
>
> thanks for the updated patch. I've applied it upstream and will be
> part of needrestart 3.6+.
>
>
> Regards,
> Thomas
>
>
>
> On 23.10.20 12:12, Lorenzo Puliti wrote:
>>
debian-b...@cboltz.de> ha scritto:
> Hello,
>
> Am Donnerstag, 29. Oktober 2020, 12:43:08 CET schrieb Lorenzo Iannuzzi:
> > apparmor="ALLOWED" operation="open" profile="syslog-
> > ng//null-/bin/dash//null-/usr/sbin/sshguard//null-/bin/journalctl"
>
Package: apparmor-profiles
Version: 2.13.2-10
Severity: important
After installing apparmor-profiles and rebooting I started receiving in log
a
lot of those messages:
localhost kernel: audit: type=1400 audit(1603955977.468:2281):
apparmor="ALLOWED" operation="open" profile="syslog-
ng//null-/bin/d
tch attached to this message.
Note that i've used 'service' instead of invoke-run, to be consistent
with upstream code, so this will need further work on Debian side,
updating and refreshing the quilt '01-use-invoke-rc.d.diff' patch.
Regards,
Lorenzo
>From 6a7ae3df50ab24c83
,
Lorenzo Puliti
-- Package-specific info:
needrestart output:
Your outdated processes:
kactivitymanage[23935], kdeconnectd[22453], kded5[6680], kdeinit5[6696],
kglobalaccel5[23942], klauncher[6697], konqueror[6620], kuiserver[22496],
lxqt-notificati[5553], lxqt-panel[5557], lxqt-policykit-[5558
the forced-rescan-test
* Fix some minor lintian tag
* Bump build-dep on dh-sysuser (>= 1.3.5)
* Bump dh compat level to 13
* d/rules: fix broken autopkgtest phony target
* d/runit.NEWS: document recent changes
* Release to unstable
Regards,
--
Lorenzo Puliti
3
Changes since the last upload:
mini-httpd (1.30-3) unstable; urgency=medium
.
[ Lorenzo Puliti ]
* QA upload.
* Fix lintian error 'init-d script not starting the service':
the service is now shipped as disabled with Sysv
* Warn users of changes in /etc/default/mini-ht
or unknown onupgrade string
* Bump debhelper compat to 13
* Use d/clean instead of override in d/rules
* Runit-helper: use explicit 0 exit status for return
* Release to unstable
Regards,
--
Lorenzo Puliti
https://salsa.debian.org/Lorenzo.ru.g-guest/dh-sysuser/-/commits/1.3.5-release/
Changes since the last upload:
dh-sysuser (1.3.5) unstable; urgency=medium
.
[ Lorenzo Puliti ]
* Do not pollute namespace in maintscript
* Do not impose unneeded dependency on sysuser-helper
* Bump
users.
Despite the apparent inaction on this bug, I'm still thinking on a
possible different solution.
Regards,
Lorenzo
updated the Maintainer to Debian QA
> Group (package has been orphaned) and fixed Bug #969063.
This package is marked for autoremoval and will be removed
in a week from now:
please file a proper RFS bug on debian-mentors list.
Best Regards,
Lorenzo
[1] https://salsa.debian.org/fmneto-guest/fgett
5
* runit-run: don't stop the service on upgrade (systemd)
* runit-run: rescan inittab on install/remove (sysvinit)
Regards,
--
Lorenzo Puliti
n/control.modules.in from
Depends: linux-modules-_KVERS_ | linux-image-_KVERS_
to
Depends: linux-modules-_KVERS_ | linux-image-_KVERS_ |
linux-image-_KVERS_-unsigned
works for me.
Thanks,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, '
: dh-runit
Version : 2.10.0
Upstream Author : Lorenzo Puliti
* URL : https://salsa.debian.org/debian/dh-runit
* License : GPL-3+
* Vcs : https://salsa.debian.org/debian/dh-runit
Section : admin
It builds those binary packages:
runit-helper
ere are a couple of lines
that ends with '|| true' and i'm afraid i still need to do that
for now.
patch available on salsa, see
https://salsa.debian.org/Lorenzo.ru.g-guest/dh-runit/-/commit/a141af7e6bbd3068ad4e239f049c332620fbce30
Regards,
Lorenzo
-- System Information:
Debian
Package: runit-helper
Version: 2.9.0
Severity: minor
Several blocks of runit-helper's code are just transition code that sooner or
later
can be removed. to be on the super-safe side we can wait up to Bookworm
release, but Bullseye
should be safe too.
Reminder:
* Loguser transition
* Moving supe
Package: src:dh-runit
Version: 2.9.0
Severity: normal
The testsuite is disabled on armhf, see #954190
Do not forget to test if the problem is fixed and reenable the testsuite
on armhf
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1,
Package: src:dh-runit
Version: 2.9.0
Severity: wishlist
The package has already an autopkgtest that checks dh-runit when it is used
to build a package, but it miss a test for runit-helper.
Runit-helper is called during packages install/remove/upgrade and an issue
there can cause a break on systems
Package: dh-runit
Version: 2.9.0
Severity: normal
After a long discussion [1][2] with init-system-helper's maintainers it looks
like it's a
good idea to decouple runit support from invoke-rc.d and update-rc.d.
Dh-runit already has support for enabling and disabling services, but
it lacks support
Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093
Dear Robby and Maintainer,
to avoid the described failure in running podman *as a regular user*, it's
enough to execute the command:
$ echo 'runtime = "crun"' > ~/.config/containers/libpod.conf
afterwards, both
$ podman info
an
Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093
Dear Robby and Maintainer,
while I can confirm `podman` doesn't correctly execute the `crun` runtime when
started from a regular user, after executing the following command from the
user's shell:
$ echo 'runtime = "crun"' > ~/.c
Thank You!
Lorenzo
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "dh-runit"
* Package name: dh-runit
Version : 2.9.0
Upstream Author : Dmitry Bogatov, Lorenzo Puliti
* URL : https://salsa.debian.org/debia
Package: opentmpfiles
Followup-For: Bug #952897
Control: tag -1 patch
Hi,
the following MR on Salsa might fix this bug
https://salsa.debian.org/debian/opentmpfiles/-/merge_requests/2
Best Regards,
Lorenzo
Package: runit
Version: 2.1.2-36
Followup-For: Bug #953875
Control: tag -1 patch
There is an open RFS bug (#960940) on mentors that fixes this bug.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960940
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
Package: dh-runit
Version: 2.8.15
Severity: normal
Tags: patch
It looks that when the 'presubj' option is set and the package ships it's own
presubj file (using package.bug-presubj), dh-runit completely overwrites the
presubj
file from the package.
Thanks to Colin Watson for spotting this.
A quic
Package: runit-helper
Version: 2.8.15
Severity: normal
Tags: patch
The following code
if [ "${ENABLE}" = yes ] && \
[ ! -h "/etc/runit/runsvdir/default/.$NAME" ] ; then
ln -sf "/etc/sv/$NAME"
"/etc/runit/runsvdir/default/$NAME"
creates a loop of symlinks
Package: dh-runit
Version: 2.8.15
Severity: important
Tags: patch
Runit recently changed the loguser from runit-log to _runit-log; dh-runit
now ships a logservice that uses the new loguser, but the appendant log
service will fail to start if the 'current' and 'lock' files inside the
logservice
di
Package: src:dh-runit
Followup-For: Bug #954190
This is probably a bug in libghc-shake-dev, for example the changelog of
haskell-shake that says
' * Disable testsuite on armhf, fails on Ubuntu builders, probably
due to a misalignment bug due to 64bit kernel. '
-- System Information:
Debian
unit/runit_2.1.2-37.dsc
updated git repo:
https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/release-2.1.2-37
Best Regards,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
A
un (Closes: #953875)
* Add lintian overrides for manpage without executable
* Update copyright for debian files
* Add an autopkgtest to catch regression on 953875
Regards,
--
Lorenzo Puliti
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500,
tested in docker and using the 'env runitdir=isolation' option works as
expected.
Of course, in your Dockerfile, you need to symlink your runit service into
/etc/runit/runsvdir/isolation/ otherwise runsvdir will have nothing to
supervise.
Hope this will solve your problem, feed
disk space will be freed.
Do you want to continue? [Y/n]
I guess this is karma striking back to me from trying to dump #953875 on you..
Regards,
Lorenzo
-- Package-specific info:
-- apt-config dump --
APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
xt alternative (runit-sysv), or it will
proceed without recommends, or it will give an error?
I'm asking because there are downstreams (like Devuan) that blacklist
systemd packages
in their archive and I would like to understand what will happen there.
Regards,
Lorenzo
sysv implementation is respawned with a line in
/etc/inittab which
is a conffile of sysvinit-core. And even if I ship and maintain my own
version of inittab,
I would still have to deal with 'runit-init'.
Regards,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT
Control: tag -1 + confirmed
surprised that apt is choosing a recommend that
removes packages when another alternative recommends that does not
require to remove any package exists. I wonder under which condition apt
will choose to install the second alternative recommends if removing
packages is not enough ? Lorenzo [1] For
ugs.debian.org does. Which option(s) trigger all the output
> at the link?
>
> Thanks!
>
Hi Svante,
I think 'lintian -EviI --pedantic --show-overrides' should do that, with
some extra info displayed.
Cheers,
Lorenzo
B for BIOS
Exec: ['mount', '--bind', '/dev', '/tmp/tmpmgw2bhok/dev']
Exec: ['mount', '--bind', '/sys', '/tmp/tmpmgw2bhok/sys']
mounting proc: ['chroot', '/tmp/tmpmgw2bhok', 'mount', &#
-shake-dev maintainer,
I'm not knowledgeble of shake: is this likely a bug in shake or a bug that
need a fix on dh-runit side?
Thanks,
Lorenzo
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/armhf/dh-runit.html
-- System Information:
Debian Release: bullseye/sid
APT pr
Hi,
> If you could check out the package as it stands in the dnsmasq git repo
> before the imminent 2.81 release, that would be great.
Just builded and installed: it looks fine for me.
Thanks
Lorenzo
t is huge.
Bastian,
do you have any idea of why there is this difference?
Are you able to reproduce an output like in message#5 within a
a minimal chroot install as I have done above?
Regards,
Lorenzo
Control: affects -1 + runit-init
atch correctly fix this issue
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.9-van (SMP w/4 CPU cores; PREEMPT)
Kernel tain
been hidden by an opaque full-screen window.
Regardless of the method, the desktop in its entirety should be considered
confidential and kept hidden until authentication is complete.
Thank you,
Lorenzo
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500
Package: init-system-helpers
Version: 1.57runit1
Followup-For: Bug #924132
Control: affects -1 + runit-init
Hi,
I'm now maintaining runit:
is there any update on the progress of this bug?
If you don't have time to spend on this, would be ok
if I ask another DD for an NMU?
Than
nsmasq,logscript,presubj
In any case, if you decide to merge this and some runit-specific bug should
arise, feel
free to add me in CC, I will provide assistance.
Best Regards,
Lorenzo
MR on salsa if you prefer
Best Regards,
Lorenzo
-- Package-specific info:
Additional PHP 7.3 information
PHP 7.3 SAPI (php7.3query -S):
PHP 7.3 Extensions (php7.3query -M -v):
Configuration files:
[PHP]
engine = On
short_open_tag = Off
precision = 14
e dh-runit Multi-Arch: foreign (Closes: #939631)
.
[ Lorenzo Puliti ]
* Remove log dir on purge (Closes: #941924)
* Use .link to mark a service as disabled (Closes: #942323)
* Adopt dh-runit package
* Revert "Temporary disable testsuite due build-dependency transition"
the GR, see
http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2019-December/002888.html
* updated salsa git repo
https://salsa.debian.org/Lorenzo.ru.g-guest/runit/-/tree/2.1.2-36-release
* should be uploaded toghether with dh-runit 2.8.15
Regards,
--
Lorenzo Puliti
int?
Have you installed runit-init in the docker image, or just runit?
Is the version of runit 2.1.2-25?
Can you post details about the Dockerfile and the image you are using?
Thanks,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, '
ipt), so the maintainer probably expect you to add
a separate 'git-daemon-systemd' package.
Alternatively you can propose the maintainer to merge all inits support in one
'git-daemon' package.
Regards,
Lorenzo
the example section.
I'm not speaking at behalf of sysvinit maintainers, please here from them about
this.
Regards,
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture:
,
Lorenzo
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WA
rqbalance
so there should be no delay)
For future runit-related bugs, if you need assistance, feel free to add
the runit-team in CC.
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architect
e not tested.
[ updated patches attached ]
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint fl
her case where it exit -1 for now, so i have reworded to
'runsv: ERROR $1 in $NAME: runscript didn't exit normally'
Patches that apply you review are attached
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable&#x
s still possible that the exit code
is overlapped with the one of some daemons, for example see
smartd(8) 'EXIT STATUS' section.
Do you have a better range to suggest?
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unst
hanks,
Lorenzo
-- 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 w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: L
voke-run (from runit package)
debsums: changed file /sbin/update-service (from runit package)
>From 9d24842ffdb859894f47142925663d2aee748643 Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Wed, 30 Oct 2019 19:32:37 +0100
Subject: [PATCH] Minor improvements to invoke-run
* be verbose a
t, is it feasible in dash/POSIX?
Also some daemon may need specific code between
/lib/runit/finish-default "$1" "$2"
and
if [ "$VERBOSE" = 1 ]; then
Examples: get some daemon specific exit codes, clean up PID file...
It is not mandatory to have the 'echo' a
Package: runit
Version: 2.1.2-35
Severity: wishlist
Tags: patch
Hi,
while doing another round of testing with openssh-server i've found some
minor problem that might need a fix.
Detailed description is in git commit message.
Lorenzo
-- System Information:
Debian Release: bullseye/sid
ve a look
> How complicated would it be to create patch for
> src:git that would at least prevented regression due hidden link change?
Code will look ugly but i think it's feasible: will try to send a patch and
keep you in CC
Lorenzo
-- System Information:
Debian Release: bullseye/sid
ncluded]
-- no debconf information
-- debsums errors found:
debsums: changed file /lib/runit/invoke-run (from runit package)
debsums: changed file /sbin/update-service (from runit package)
>From fb4c08329b710b1bb276e9ecad561c16b63cb9fe Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti
Date: Thu,
pts (like git-run) will become buggy,
probably the
maintainer deserves to be warned before change in update-service happens.
I think all the above should be dealt with in #942320 rather than here, but the
two are
connected so consequences should be taken in account also here
Lorenzo
-- Syste
disabled
(and currently has no mean to do that).
I propose to use .service symlinks to mark a service as disabled (directories
starting with
dots are ignored, this is already documented in runsvdir(8) manpage).
I've documented this in update-service manpage (see #942320); maybe this need
als
rving local admin choice to keep a service disabled.
I've added some detail in the man page but I hope to provide some more
detailed info in update-rc.d man page as runit support is merged there.
Lorenzo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT po
201 - 300 of 734 matches
Mail list logo
