You are not logged in.
- Topics: Active | Unanswered
#51 Re: Other Issues » Runit » 2021-02-09 09:29:55
Hi (runit maintainer here),
If i got it, runit defaults in sysvinit when it wont find runit scripts.
During boot it first run all sysv scripts in runlevel 2, but it skips those for which a native runscript that matches the basename exists.
Then it starts all native runscripts that are enabled.
For example if you have a /etc/sv/ssh runit service, than the SNNssh sysv service will be skipped.
----------------------
I found a page with runit runscripts scripts. Should i use those?-----------------------
those are quite old, but still a good starting point for experimenting.
I maintain a collection https://salsa.debian.org/runit-team/run … collection
but please everybody, CAUTION*, those are meant to be used with runit>=2.1.2-36 and anyway are somehow experimental.
I plan to upload a catchall package that will properly install those (and more) runscripts into the system, but
it's unrealistic to expect to see it land into unstable before summer 2021.
last thing, for the brave souls that are willing to experiment, i accept requests for adding new runscripts at the condition that the person that does the request is available to test and report if it's working
Best,
Lorenzo
*especially if you are running a desktop environment, you either want to have dbus, elogind and sddm|lightdm|slim|etc.. all as runscripts or all as sysv script. Mixing wont work an you'll end up with a VT login.
#52 Re: DIY » [HowTo] runit-init as PID1 » 2020-07-21 11:16:47
Just run into this thread by chance. There is very few interest in runit in Debian right now so maybe is convenient to drop some howto directly here where it looks there are people available to do some testing..
After the reboot when I login on tty1 and run startx, it shows tint2 panel and everything, but I can't move the mouse cursor, can't do anything with keyboard and the machine freezes!! Please help!
Yes, I've just confirmed that — the user must be in the input group if a display manager isn't used.
This permission issue is new to me but is bad enough that I need to double check if this can be reproduced in Debian and possibly fix there. I'm not sure though, could be also something that is caused by some Debian-Devuan delta.
When I ran `# apt install runit-init`, it said:
...
dpkg: sysvinit-core: dependency problems, but removing anyway as you requested:
init depends on sysvinit-core | runit-init: however:
Package sysvinit-core is to be removed.
Package runit-init is not installed.
...
Unpacking runit-init (2.1.2-36) ...
Setting up runit-init (2.1.2-36) ...
Besides sysvinit-core, was any other package removed?
I'm not surprised that Xorg is not working with runit, without elogind or any other means that gives permission on input devices to your user, but what puzzles me is how was working with sysvinit..
Lorenzo
#53 Re: Other Issues » Is "opentmpfiles" for openRC a useful package? » 2020-07-21 08:51:29
Hi,
For now no, in future will be probably needed to avoid systemd lockin on certain Debian packages.
There is a commit [1] recently merged (but not yet uploaded to Debian archives) that makes opetmpfiles a dropin replacement to systemd-tmpfiles, so each package that has a dependency on systemd because of tmpfiles can use tmpfiles instead of systemd, if someone convince the maintainer of such package to change the dependency from 'systemd' to ' systemd | systemd-tmpfiles '.
Only example for now is the php7.x-fpm package that need a rebuild on Devuan right now, but will be installable once the new version of opentmpfiles will be uploaded.
Same goes for opensysusers package.
Regards,
Lorenzo
#54 Re: Off-topic » deb.sury.org now requires systemd » 2020-03-03 12:34:25
Hi Folks,
I'm running Debian Sid (without systemd), just want to give few info in the hope that are usefull:
I don't think you need to rebuild this package (althougth you are free to do so if you prefer).
I filed a bug for this with a patch
https://bugs.debian.org/cgi-bin/bugrepo … bug=952895
which was rejected because the maintainer wants opentmpfiles to be a drop in replacement to systemd-tmpfiles
https://bugs.debian.org/cgi-bin/bugrepo … bug=952897
wich will not happen before the tech commettee rules about this bug
https://lists.debian.org/debian-ctte/20 … 00003.html
Yeah...
But I mailed the php-fpm maintainer in private explaining that installing systemd will remove my desktop (because of elogind), so he added this commit
https://salsa.debian.org/php-team/php/- … e35adf50d4
In short, for now create a package that provides systemd-tmpfiles, depends on opentmpfiles and ships a symlink systemd-tmpfiles --> opentmpfiles-tmpfiles, wait for the next debian release of php7.x-fpm and it should work.
FPM starts logging this kind of thing to syslog:
[21-Feb-2020 16:22:59] NOTICE: systemd monitor interval set to 10000ms
I have this too but it looks it's working even if don't have systemd installed: it's not working for you?
Lorenzo
Board footer
