nosh on GNU/Linux: missing sys/event.h

Hello, I tried to build nosh 1.16 from source code [1]. But some programs fail to compile, complaining about a missing header, sys/event.h. Which is true: there's no event.h file on /usr/include/sys, or anywhere else on my system. Since nosh is supposed to build and run at least on Debian 7,

Re: What interrupt does Ctrl+Alt+Delete send PID1?

2015-06-12 9:44 GMT-03:00 Steve Litt: On Fri, 12 Jun 2015 11:31:44 +0200 Laurent Bercot wrote: Well, your host system will definitely catch the 3 finger salute; it won't be sent as is to your guest system. Is there a way for the VM to send an emulated ctrl-alt-del press to the guest ?

Re: s6: compatibility with make3.82

Hello, 2015-08-07 20:29 GMT-03:00 Buck Evan: s6-user@696f14e9c9bd:~/scratch$ /opt/make/make make: *** No rule to make target '-lc', needed by 'all'. Stop. s6-user@696f14e9c9bd:~/scratch$ /opt/make/make --version GNU Make 4.1 Built for x86_64-unknown-linux-gnu That's not strange. This is

Re: s6: compatibility with make3.82

2015-08-08 15:49 GMT-03:00 Laurent Bercot: Not using vpath would result in not checking external libraries (so, fo instance, failing to rebuild if libskarnet.a changes) And I don't know why you would want to do that. Software packages usually don't bother; external libraries are at most

Re: supervision-scripts 2015-06

2015-07-08 22:07 GMT-03:00 Avery Payne: + A small comparison table has been added to the wiki, showing 6 different frameworks and their various related concepts. It is incomplete but somewhat usable, and contains various links to sites, downloads, etc. Because there is still a lot of missing

Re: nosh: service-dt-scanner gets repeatedly killed by SIGABRT

2015-07-06 22:01 GMT-03:00 Guillermo: > > I wanted to try out nosh daemontools-style, i.e. using > service-dt-scanner and launching service-manager "by other means" > [...] > However, under certain circumstances service-dt-scanner receives a > SIGABRT signal and dies

Re: nosh: service-dt-scanner gets repeatedly killed by SIGABRT

2015-07-08 5:30 GMT-03:00 Jonathan de Boyne Pollard: If there's no error output, crank up strace and see what the last few system calls are. It's probably worthwhile doing that anyway, in fact. Here are the last system calls shown by an strace of service-dt-scanner before the SIGABRT, with

Re: [ale] systemd talk from July has slide deck online now

2015-09-09 2:04 GMT-03:00 Steve Litt: > > If I want to use s6 as my init, what do I do, just put into my Grub > kernel line init=/usr/bin/s6 or whatever the s6 executable is? If you want to use the s6-linux-init package and minimum customization, in addition to s6 and s6-linux-init, you'll need

Re: nosh version 1.19

2015-08-22 15:04 GMT-03:00 Jonathan de Boyne Pollard: > > nosh is now up to version 1.19 Hi, I had some issues with the source package I thought I should mention: * source/common-manager.cpp wouldn't compile on my Gentoo system, because this new version calls setrlimit(), and makes use of struct

Re: nosh version 1.23

2015-12-17 10:50 GMT-03:00 Jonathan de Boyne Pollard: > > The nosh package is now up to version 1.23 . Hi, It seems that the 'unload-when-stopped' and 'version' subcommands of system-control are not mentioned in the documentation. They are listed in the output of 'system-control --help', though.

Re: How to make svlogd send logs via UDP

2016-02-06 2:25 GMT-03:00 Nicolas de Bari Embriz Garcia Rojas: > > also wondering if it is posible to use a domain name instead of an IP If you mean in the u or U lines of the config file, then no, they only accept an IPv4 address. G.

Re: nosh version 1.28

Hi, 2016-08-06 14:30 GMT-03:00 Jonathan de Boyne Pollard: > > The nosh package is now up to version 1.28 . Could the plain 'setlock' invocation in script source/default.html.do be changed to './exec setlock', as in scripts source/default.1.do and source/default.8.do, please? Otherwise we have

Re: nosh version 1.31

2017-01-22 14:29 GMT-03:00 Guillermo: > > $ tai64nlocal /run/system-manager/log/current > [...] > 2017-01-21 22:11:17.709678664 system-manager: ERROR: > /sys/fs/cgroup/systemd//cgroup.subtree_control: No such file or > directory > 2017-01-21 22:11:17.709683364 system-mana

Re: s6-linux-init: SIGUSR1 and SIGUSR2

2016-08-21 6:15 GMT-03:00 Laurent Bercot: > > On 21/08/2016 06:18, Casper Ti. Vector wrote: >> >> It seems that the exchanging of SIGUSR1 and SIGUSR2 [1] in s6-linux-init >> did not happen. Is it just forgotten, or ...? > > Well, by the point I remembered to make the change, I already had >

Re: s6-linux-init: SIGUSR1 and SIGUSR2

2016-08-22 7:15 GMT-03:00 Laurent Bercot: > > The next s6+friends version release will have major version bumps all > around, so compatibility is moot anyway. If you really think it's worth it > to swap SIGUSR1 and SIGUSR2, I'll do it. It would be more aesthetically pleasing if s6-halt sent

Re: How to trap ctrl-alt-del?

2016-11-25 6:28 GMT-03:00 Colin Booth: > > On Nov 25, 2016 3:53 AM, "Casper Ti. Vector" wrote: >> >> On Fri, Nov 25, 2016 at 11:07:15AM +0300, Jean Louis wrote: >>> >>> How may I trap ctrl-alt-del, >> >> $ sysctl kernel.ctrl-alt-del=0 > > This is a bit misleading since most (all?) default builds

Re: Adding capability control into the `run' script comparison page

2016-12-07 6:26 GMT-03:00 Jean Louis: > > On Wed, Dec 07, 2016 at 09:14:00AM +, Jonathan de Boyne Pollard wrote: >> [...] >> To anyone running the service manager and bundles from nosh version 1.28 or >> later on Linux: You are encouraged to look at your control group hierarchy, >> with a

s6-rc: Managing small changes to the active services database

Hello, Consider a fully s6-rc-managed machine. Such a machine would have an 'active' services database (the compiled database linked from s6-rc's live state directory), and some place where service definitions would be stored in source format. The active services DB would have been initially

nosh: service-control --exit

Hello, 2016-08-06 14:30 GMT-03:00 Jonathan de Boyne Pollard: > > svc -x > == > > The -x option to service-control, a.k.a. svc, is no longer defunct. It does > what unload-when-stopped does. There is a minor difference: for some reason 'service-control --exit' doesn't unload a service that is

Re: nosh version 1.33

2017-04-09 16:52 GMT-03:00 Jonathan de Boyne Pollard: > > The nosh package is now up to version 1.33 . > > [...] > > More packages > - > > There are now four more -shims packages, for commands whose names conflict > with > commands from other packages: nosh-kbd-shims, nosh-bsd-shims,

Re: nosh version 1.34

Hi, 2017-07-05 17:41 GMT-03:00 Jonathan de Boyne Pollard: > > The nosh package is now up to version 1.34 . So, system-control has a new but undocumented 'is-service-manager-client' subcommand? G.

Re: s6-svscanboot, how to exit?

2017-07-14 13:00 GMT-03:00 Jean Louis: > > However, the VPS servers don't have much option > left to me, I can install my own system with s6, > or I can use the ready Debian, Ubuntu and similar. OK, quick summary if you are stuck with systemd but want the least possible interaction with it, and a

Re: s6 as a systemd alternative

Hello, 2017-06-26 12:05 GMT-03:00 Istvan Szukacs: > > [...] I do not want > logging, ntp and all the other crap that got sucked into it. I understand > that service files are much better that shell scripts and this is a good > argument but it does not justify the idiocracy that systemd became in

Re: s6 as a systemd alternative

2017-06-28 14:40 GMT-03:00 Steve Litt: > > On Mon, 26 Jun 2017 14:53:50 + "Laurent Bercot" wrote: >> >> The problem with the runit model is that it is pure supervision - >> it does not provide service management. You have to run all your >> oneshots _before_ you can start longruns. > > Not

Re: s6 as a systemd alternative

2017-06-29 1:43 GMT-03:00 Steve Litt: > > On Wed, 28 Jun 2017 22:31:12 -0300 Guillermo wrote: >> >> But then you end up with an unsupervised runsv process, disconnected >> from the rest of the supervision tree... > > I'm not sure about the unsupervised part of it,

Re: Problems with Step 4

Hi, 2017-06-27 16:51 GMT-03:00 Daniel GSJ: > > Once stage 2 is reached, the computer hangs in the same way than when > executing *agetty* in an active console tty, and doesn't login neither. > > My o.s. is build with Linux-from-scratch, and is running SystemV, so it is > a pretty simple system. >

Re: Why /command ?

2017-07-01 20:37 GMT-03:00 Steve Litt: > > So I was wondering what the original intent was in having these two > directories directly off the root? Is it so the init and supervision > can proceed even before partition mounts are complete? Is there some > other reason? It has been mentioned in

Re: A dumb question

Hi, 2017-05-02 6:32 GMT-03:00 Francisco Gómez García: > > May 2, 2017 8:35 AM, "Steve Litt" wrote: > >> I also am surprised you could get Gnome to work without systemd. Just >> for fun, try out LXDE, and install dmenu and have it at the ready >> with an easy hotkey. I think you'll love the

Re: New reboot flag: -c for 'power cycle'

(Quoting this e-mail for context) 2017-10-29 5:37 GMT-03:00 Jonathan de Boyne Pollard: > > Since SIGWINCH to process #1 is already taken by Linux, I have adjusted my > softwares to use SIGRTMIN+7 and SIGRTMIN+17 for the signals to process #1 > for this, ready for when Linux eventually catches up

Re: New reboot flag: -c for 'power cycle'

2017-10-29 18:01 GMT-03:00 Laurent Bercot: > > Maybe, if it's needed. SIGWINCH is not POSIX, and I'd rather not have > s6 exhibit different behaviours on systems where it's not supported > (same reason why I'm reluctant to add pid namespace support to > s6-supervise). If there's a way to make it

Re: New reboot flag: -c for 'power cycle'

2017-10-29 22:24 GMT-03:00 Guillermo: > > [...] or to call a program that does this reboot(RB_POWERCYCLE) thing > on FreeBSD, if it's implemented. Scratch this part; it would have to be called by the stage3 init, not the SIGWINCH handler. But it was an example, the rest of the mess

s6-rc live state and database format upgrades

Hello. I was recently reviewing the instructions for the s6-rc dabatase upgrade procedure, and they made me wonder what would happen if: * s6-rc-format-upgrade was called with a compiled database that is not the exact 0.4.0.x equivalent of the one currently associated with the live state

Re: has anyone gotten nosh to build on Void Linux?

Hi, 2018-06-30 5:44 GMT-03:00 Chris Brannon: > > When I run package/compile from the root of the unpacked source tree, I > get: > redo: ERROR: all: Cannot find .do file to use. > > -- Chris The nosh-1.37 source package? If you unpacked the source tarball in a directory named 'nosh-1.37', you

Re: has anyone gotten nosh to build on Void Linux?

2018-06-30 21:27 GMT-03:00 Chris Brannon: > > Sorry, I didn't have time to reply, but I made a good deal of progress > earlier today, after writing to the list. Great! > I also needed to fine libtinfo, because > Void doesn't have it. Void could probably have libtinfo provided by > their curses

Re: has anyone gotten nosh to build on Void Linux?

2018-07-01 8:38 GMT-03:00 Jonathan de Boyne Pollard: > > For the sake of other readers: note that it is not the build system that > employs the wall program. (That would be bizarre.) It is the shutdown > program, at runtime, as described in its manual. Yep, that is a runtime dependency rather

Re: execlineb's import conflicts with ImageMagick

Hello, 2017-10-22 18:01 GMT-03:00 Jean Louis: > > The ImageMagick software has the "import" command > that is conflicting with "import" from execlineb > package. This is known, see the 'execline-2.3.0.0' section of this announcement: *

Re: nosh build problems (Re: Compatibilities between runit and s6 (re: )

2018-01-16 17:51 GMT-03:00 Jonathan de Boyne Pollard: > > Charlie Brady: > >> /usr/include/curses.h:843:31: error: initializing argument 1 of 'char* >> tigetstr(char*)' [-fpermissive] >> >> service-status.cpp:148:21: error: invalid conversion from 'const char*' to >> 'char*' [-fpermissive] >>

Re: nosh version 1.37

2018-02-20 16:13 GMT-03:00 Jonathan de Boyne Pollard: > > Guillermo: >> >> redo-ifchange[2]: ERROR: services/dbus-broker.service: Not done. >> redo-ifchange[2]: ERROR: services/dbus-daemon.service: Not done. >> redo-ifchange[2]: ERROR: services/system-wide.conf

Re: nosh build problems (Re: Compatibilities between runit and s6 (re: )

2018-01-16 13:09 GMT-03:00 Charlie Brady: > > Now seeing these many times: > > /usr/include/curses.h:843:31: error: initializing argument 1 of 'char* > tigetstr(char*)' [-fpermissive] > > service-status.cpp:148:21: error: invalid conversion from 'const char*' to > 'char*' [-fpermissive] >s =

Re: nosh version 1.37

2018-02-18 20:05 GMT-03:00 Jonathan de Boyne Pollard: > > Guillermo: > >> This is going to happen for every [GNU/]Linux distribution that is not >> Debian, Arch, CentOS or RHEL. It does not... uh... look very portable :/ >> > > That is a reflection of reality.

Re: nosh version 1.37

2018-02-18 3:49 GMT-03:00 Jonathan de Boyne Pollard: > > The nosh package is now up to version 1.37 . > [...] >Per-user management has been augmented, finally fixing the problem >of |system-control| locating the per-user manager by giving the >per-user manager an optional listening

Re: G++ warnings for set-control-group-knob from nosh-1.37

2018-03-11 20:57 GMT-03:00 Jonathan de Boyne Pollard: > > The macro generates no warning in the GNU C library in Debian 9, but I > should have caught that overload that was not passing by reference. It is > fixed now, thank you. The in-development source archive for 1.38 is in the > usual place.

Re: [announce] execline-2.5.0.0

2018-04-02 7:39 GMT-03:00 Laurent Bercot: > > User reports have come in by the hundreds and they are almost > unanimous (sorry, Colin): they don't like the 2.4.0.0 change, > pretending it hurts readability (as if), and writability too, > of execline scripts. (What? People were actually writing

Re: Noclobber supervisor/init installation

Hello, El sáb., 27 oct. 2018 a las 16:12, Steve Litt escribió: > > So I've created the following terminology: > > du: Daemons used. Refers to the symlink directory or its > subdirectories. /service in the original daemontools is an example > of a du directory. /etc/sv in both Void Linux

Re: Log rotation issue with runit

El jue., 27 dic. 2018 a las 6:36, Dmitry Bogatov escribió: > > And this issue happens not only on crash, it happens after every > termination of svlogd, due any signal. I would agree that SIGKILL is > crash, but issue reproduces with SIGINT and SIGTERM. SIGTERM should make svlogd exit cleanly,

Re: Log rotation issue with runit

El jue., 27 dic. 2018 a las 10:47, Steve Litt escribió: > > [...] Simply run a program, invoked by cron, > that deletes .u files over a certain age, as long as it doesn't delete > the latest .u file. Daemontools-style loggers like svlogd delete files themselves during a rotation for a reason,..

Re: Log rotation issue with runit

El sáb., 29 dic. 2018 a las 15:33, Dmitry Bogatov escribió: > > > > And this issue happens not only on crash, it happens after every > > > termination of svlogd, due any signal. I would agree that SIGKILL is > > > crash, but issue reproduces with SIGINT and SIGTERM. > > > > SIGTERM should make

nosh: User-space virtual terminal test and questions

Hello, So, I've gotten around to testing user-space VTs with nosh tools on Gentoo, as described in the nosh Guide. Mostly console-fb-realizer, but I also tested console-termio-realizer on a kernel VT for comparison. This was in a VirtualBox VM, so there were two framebuffer devices available: the

Re: s6-ps

El sáb., 5 ene. 2019 a las 7:46, Jonathan de Boyne Pollard escribió: > > * https://packages.debian.org/sid/s6 And buster too. Which has the side effect of making it automatically available in Devuan ceres and beowulf :) * https://pkginfo.devuan.org/cgi-bin/d1pkgweb-query?search=s6_2.7=any I

Re: More Answers

El lun., 24 dic. 2018 a las 7:10, Laurent Bercot escribió: > > >* https://unix.stackexchange.com/a/489949/5132 > > > >This may be of interest to people looking for some (brief) comparative > >analysis. Including the further reading. (-: > > Thanks for the heads-up! I posted an answer in

Re: Log rotation issue with runit

El mar., 25 dic. 2018 a las 10:39, Dmitry Bogatov escribió: > > Hello! > > I am Debian maintainer of `runit' supervision suite. Recently, I > received bug report [^1] about stray .u logfiles. After some > investigation I found code, that caused issue, but it seems that it was > written with some

Re: Log rotation issue with runit

> […] Both .u and .s files are supposed to > be deleted when they are the oldest file in the logging directory, to > honor 'u' lines in 'config' files, […] Sorry, that should have read: to honor 'n' lines in 'config' files. G.

Re: s6 problems logging

Hello, El dom., 27 ene. 2019 a las 15:56, Sean MacLennan escribió: > > So it seems that s6-log does not like buffered output. It probably isn't that it doesn't like it, but that it doesn't even get to see the output. As Jonathan also pointed out, when you run doorknob using a supervision suite,

Re: what init systems do you use ?

El jue., 2 may. 2019 a las 21:53, Jeff escribió: > > what init systems do this list's subscribers use ? I have a Gentoo setup with no initramfs and one of the stable desktop profiles (in the 'eselect profile' sense, which means GNU libc with dynamic linking), that allows me to boot with an

Re: interesting claims

El dom., 19 may. 2019 a las 8:24, fungal-net escribió: > > [...] > This is Adélie adelielinux.org > installation on HD. Although it is confusing to me how they set this up > still, after months of following its development (beta3), there is > sysvinit on the first steps of booting then OpenRC

Re: killall test run

El dom., 19 may. 2019 a las 9:57, Jeff escribió: > > OpenRC is known to work with s6-svscan (this is done via the > /libexec/rc/sh/s6.sh shell script). That is part of OpenRC's s6 integration feature, and, although on the surface it looks like a nice thing to have, the implementation of it

Re: interesting claims

Hi, El vie., 17 may. 2019 a las 8:22, fungal-net escribió: > > OpenRC: Nice, > init >|_ zsh > when I exited the shell there was nothing but a dead cursor on my screen May I ask what was this setup like? You made a different entry for sysvinit, presumably with the customary getty

Re: s6-log problem with +regex

Hi, El jue., 9 may. 2019 a las 22:03, Dewayne Geraghty escribió: > > My test comprised an input /tmp/af with the intention of > four separate s6-log managed logdirs. The logdirs' structure was > correctly created, however three contained the same content, and the > default contained nothing. So

Re: further claims

El mar., 30 abr. 2019 a las 5:55, Laurent Bercot escribió: > > >haven't you claimed process #1 should supervise long running > >child processes ? runit fulfils exactly this requirement by > >supervising the supervisor. > > Not exactly, no. > If something kills runsvdir, then runit immediately

Re: interesting claims

El lun., 29 abr. 2019 a las 16:46, Jeff escribió: > > "suckless init is incorrect, because it has no supervision capabilities, > and thus, killing all processes but init can brick the machine." > > a rather bold claim IMO ! > where was the "correct" init behaviour specified ? > where can i learn

s6-linux-init-1.0.0.0 (was: special s6-svscan/perp(d) catch-all logger service option)

Hi, El jue., 25 abr. 2019 a las 20:10, Laurent Bercot escribió: > > I would recommend you to grab the 0.4.0.1 release of s6-linux-init > and use the stage 1 scripts created by s6-linux-init-maker, either as > is, or as a source of inspiration for your own stage 1 scripts. > [...] > I would also

Re: s6-linux-init: Actions after unmounting filesystems

El sáb., 17 ago. 2019 a las 20:01, Laurent Bercot escribió: > > - If a filesystem can track all the processes that have a handle on > it, it is possible to have it be mounted/unmounted symmetrically by > the service manager. I don't think there are filesystems that can do that? > At unmount

Re: s6-linux-init: Actions after unmounting filesystems

El dom., 18 ago. 2019 a las 15:36, Laurent Bercot escribió: > > >Simply excluding filesystems doesn't help when the root filesystem is on one > >of > >these devices that needs teardown actions after being unmounted. In that > >case, > >the only workable solution is to have PID1 pivot_root() to a

s6-linux-init: Actions after unmounting filesystems

For the 0.4.x.x series of s6-linux-init, the shutdown sequence model was that s6-svscan replaced itself with a 'stage3 init' that ran as process 1 until the machine halted, powered off, or rebooted. The stage3 init was an execline script. s6-linux-init-1.0.0.0 and later, among other things, has

Re: s6-log can create current with 640?

El vie., 25 oct. 2019 a las 5:22, Dewayne Geraghty escribió: > > Results for umask > rm -f /tmp/t1 ; /usr/local/bin/execlineb -Pc 'redirfd -w 1 /tmp/t1 umask > 037 echo hello' ; echo $? ; ls -l /tmp/t1 > [...] > I've placed the ktrace's dumpfile in txt format so its readable for you at >

Re: The "Unix Philosophy 2020" document

El dom., 17 nov. 2019 a las 4:28, Casper Ti. Vector escribió: > > A system proponent gave a remark about nosh's `move-to-control-group', > which appears, to some degree, justified: > Those are just two if statements 'sharing' a body for

Re: s6 usability

El sáb., 21 dic. 2019 a las 6:26, Jan Braun escribió: > > > > 1) Debian ships with a working and maintained runit-init package. > [...] > > I hear you. Unfortunately, I have no control over what Debian does. > [...] > If you're referring to >

Re: runit SIGPWR support

The keyboard signal can actually be set to any signal less than or equal to NSIG with the KDSIGACCEPT ioctl. sysvinit just happened to pick SIGWINCH for that, and so did systemd and nosh, presumably for compatibility. El dom., 23 feb. 2020 a las 20:53, Laurent Bercot escribió: > > Both SIGPWR

Re: runit SIGPWR support

El mar., 25 feb. 2020 a las 6:08, Jonathan de Boyne Pollard escribió: > > Laurent Bercot: > > Of course, but once the fd is closed, /dev/console should not have > > any impact on the process, so would a kbrequest still reach it? > > Yes. Also, I tested it :) I added an open2("/dev/tty0",

Re: runit SIGPWR support

El lun., 24 feb. 2020 a las 19:25, Laurent Bercot escribió: > > I purposefully did not add a default SIGWINCH handler, because > sysvinit does not come with a default kbrequest in /etc/inittab. > I added a SIGPWR handler that performs a regular poweroff because > it sounds like a sane default

Re: runit SIGPWR support

El lun., 24 feb. 2020 a las 19:49, Laurent Bercot escribió: > > So there is no fd to call the ioctl on, and no way for a user to trigger > a kbrequest. s6-linux-init has a suitable open file descriptor. It is its standard input, before it closes it to do the slashdev test. G.

Re: The "Unix Philosophy 2020" document

El sáb., 28 dic. 2019 a las 11:06, Alex Suykov escribió: > > Minor note on this. Resource limiting with cgroups does not require > any explicit support from s6, or any external tools for that matter. > Literally just `echo $$ > $cg/cgroup.procs` in the startup script > is enough, assuming the

Re: The "Unix Philosophy 2020" document

El vie., 27 dic. 2019 a las 20:56, Oliver Schad escribió: > > Sorry, I have to correct that a bit: you can use the freezer cgroup as > I did, but there is no guarantee, that you can successfully kill a > freezed process. You can't? So the 'kill -9' command in your script might not work while the

Re: [request for review] Port of s6 documentation to mdoc(7)

Hello, El dom., 30 ago. 2020 a las 7:01, Laurent Bercot escribió: > > That would be totally awesome. However, I'd hold off on s6-rc for now, > because I'm in the process of exploring a possible redesign (for better > integration of features that distributions want before packaging and > using

Re: Module-load binary for S6

Hello, El vie., 9 oct. 2020 a las 9:19, Amaresh Kotekal escribió: > > Is the module-load binary is available for S6 to load all the kernel module > ? Just in case the actual question you wanted to ask was "how do I get functionality equivalent to that of the systemd-modules-load program with an

Re: Runit source version control

El dom., 16 ago. 2020 a las 11:56, Érico Nogueira escribió: > > I was looking into runit version history, and was wondering if there's > anywhere I could access actual version control of its source. There is a Git repository, actually: git clone http://smarden.org/git/runit.git/ Source:

Re: Following log directories

El jue., 25 jun. 2020 a las 10:20, Guillermo escribió: > > El jue., 25 jun. 2020 a las 6:27, Carl Winbäck escribió: > > > Does anyone know if the follow-log-directories tool[1] from the nosh > > suite is compatible with logs produced by s6-log? > > Let's find out. I'll

Re: Following log directories

El sáb., 27 jun. 2020 a las 4:59, Jonathan de Boyne Pollard escribió: > > John W Higgins wrote: > > > I meant nothing towards s6 - but daemontools does not deal with leap > > seconds (or at least it cetainly looks that way from my foolish > > viewpoint). > > > daemontools very much *does* deal in

Re: Following log directories

Hi, > Does anyone know if the follow-log-directories tool[1] from the nosh > suite is compatible with logs produced by s6-log? Let's find out. I'll test that. G.

Re: s6-supervise: use of nosetsid

El jue, 3 dic 2020 a las 13:47, Laurent Bercot escribió: > > I have previously added the "nosetsid" feature to s6-supervise, to > address the issue: [...]. So when people want to manually > test a supervision tree, they can have nosetsid files in their test > service directories, and ^C will

Re: s6-supervise: use of nosetsid

El jue, 3 dic 2020 a las 18:34, Laurent Bercot escribió: > > So, can you juggle fds to avoid nosetsid, or can't you do the same > thing without it? This particular use of nosetsid can probably be implemented in some other way. I did think about having supervision tree processes inherit a FD for

Re: writing s6 services

El mar., 3 nov. 2020 a las 8:48, billa chaitanya escribió: > > >So, Is there any variable we can use inside run or finish > > script of a service equivalent to the pid of the process started inside > > run script? The PID of the supervised process will be the same as that of the

Re: S6 bundle

Hi, Strictly speaking, you should say "s6-rc bundle", not "s6 bundle". El mar., 20 oct. 2020 a las 13:00, Amaresh Kotekal escribió: > > Contents of S6 bundle will run serially one after the other or they will > run parallely ? Specifying the name of a bundle in an 's6-rc -u change' command with

Re: Dependencies in S6

El mié., 21 oct. 2020 a las 7:10, Amaresh Kotekal escribió: > > Secnario 1: > 1. A & B are one shot services in a s6-rc bundle. Service B is dependent on > A. ( added in dependency file). > 2. I think Service B will start after the completion of service A ( A then > B, in serial manner ) is it

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El jue, 28 ene 2021 a las 7:08, Casper Ti. Vector escribió: > > I did not actively follow the recent evolution of s6, and have just been > bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used > of course) when it comes along with other updates. > > [1]

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El vie, 29 ene 2021 a las 0:07, Casper Ti. Vector escribió: > > Not using s6-linux-init has never been an explicit goal, [...] > > Currently I do not understand the `s6-linux-init-shutdown(d)' way > well, so the old-fashioned way is retained at least for now, [...] Forgive me if I'm

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El vie, 29 ene 2021 a las 14:27, Guillermo escribió: > [...] Huh. Lots of apostrophes that shouldn't be there, and that I just couldn't see without a fixed width font... G.

Re: runit: why ignore SIGCONT for stages?

This was meant for the mailing list. I accidentally replied to the author instead. Sorry Leah! El mar, 23 nov 2021 a las 9:18, Leah Neukirchen escribió: > > [...] This seems to be due to runit(8) before execing > into the stages: > > sig_unblock(sig_cont); > sig_ignore(sig_cont); >

Re: s6 xinit replacement?

El sáb, 14 may 2022 a las 22:52, Laurent Bercot escribió: > > [...] it *is* possible to run Xorg under s6; several users are > doing so, and I hope they will post their setup. I actually don't run Xorg as a supervised process. I don't know what systemd-based GNU/Linux distributions do, but on

Re: s6 xinit replacement?

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: Operation not permitted > (EE) > Fatal server error:

Re: s6 xinit replacement?

if its binary might not be suid (its helper, Xorg.wrap, is). If your setup works in a way that does not involve elevated privileges, to be honest, I'd rather read about *that* instead of yet another systemd / RedHat / IBM rant. > Again, sorry Guillermo, this is not personal [...] No worries, no offense taken. G.

Re: s6 xinit replacement?

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]. > > [1]: https://github.com/smaeul/rc-user > [2]: https://github.com/smaeul/rc I had a

Re: gpg-agent runit run script

El mar, 20 sept 2022 a las 18:51, João escribió: > > I would like to have gpg-agent running under runit supervision on a user > runsvdir, but I have been unable to write a run script that works. > Would anyone have an example run script for gpg-agent, or be able to offer any > pointers? As

Re: gpg-agent runit run script

El jue, 29 sept 2022 a las 9:22, Alexis escribió: > > João Pedro Malhado writes: > > > The Void linux manual shows gpg-agent running as an example, but > > they > > don't show > > the run script, so I don't know how they set it up. > > https://docs.voidlinux.org/config/services/user-services.html

Re: s6-rc user services on Gentoo

El mié, 3 abr 2024 a las 8:37, Laurent Bercot escribió: > > >2) The presence of a notification-fd file tells s6 that dbus-daemon > >can be somehow coerced into producing an s6-style readiness > >notification using file descriptor 3 without changing its code, are > >you sure that's the case with

Re: s6-rc user services on Gentoo

Hello, El mar, 2 abr 2024 a las 1:42, Alexis escribió: > > > S6RC_SERVICE_REPO=${HOME}/src/srht/gentoo-overlay/sys-apps/s6-rc-services/files/ > > * The above directory contains two service directories: > ** dbus-session-bus/, containing: > *** type: longrun > *** notification-fd: 3 > ***