Re: s6-rc user services on Gentoo
On Sat, Apr 6, 2024, 19:43 Guillermo wrote: > But then, there is a problem if one actually wants the server address > information that --print-address provides. Alexis' 'run' script for > example wants to save that to a file (apparently in a directory > suitable for s6-envdir). If the output is sent to the notification > pipe instead, s6-supervise will 'eat' it while waiting for the final > newline character, and then the information is lost. > > And more generally, there's also the question about how 'ready' > dbus-daemon actually is when the point in its code that prints the > server address is reached. I can't really say without looking at the > code; dbus-daemon has many duties once its UNIX domain socket is > bound. > > G. > I have been using `--print-pid=3` as readiness notification for dbus-daemon for quite a while now on my user services and I haven't had any problems with it so far. IIRC, looking at dbus-daemon code, it actually prints the socket address first then its pid. So, I use the `--print-address=` option to save the socket address to a file for consumption by s6-envdir. >
Re: "emptyenv -c" unsets all environment variables
No problem, waiting for the next update then. Thanks! MMS On Sat, Jan 23, 2021, 18:16 Laurent Bercot wrote: > >Unfortunately, after updating to skalibs-2.10.0.1 (downloaded from > https://skarnet.org/software/skalibs/skalibs-2.10.0.1.tar.gz) and > recompiling execline (statically linked) the problem persists. I also tried > compiling and installing both of them on clean system (no previous versions > of skalibs and execline installed before) and "emptyenv -c" still empties > the whole environment. Perhaps I'm missing something? > > My bad! I lied, skalibs-2.10.0.1 fixes something else. The bugfix > for emptyenv -c is in the execline git master, but I haven't cut a > release yet. Sorry! > I will release versions for execline (and s6, which also has > bugfixes) early next week. > > -- > Laurent > >
Re: "emptyenv -c" unsets all environment variables
My apologies for not checking for updates first, I'll actively check for updates before posting here next time :D. Unfortunately, after updating to skalibs-2.10.0.1 (downloaded from https://skarnet.org/software/skalibs/skalibs-2.10.0.1.tar.gz) and recompiling execline (statically linked) the problem persists. I also tried compiling and installing both of them on clean system (no previous versions of skalibs and execline installed before) and "emptyenv -c" still empties the whole environment. Perhaps I'm missing something? On 22 Jan 2021 16.39, Laurent Bercot wrote: I'm using skalibs-2.10.0.0 and execline-2.7.0.0 here in my system. I noticed on my system that "emptyenv -c" unsets all environment variables just like "emptyenv" does. This didn't happen with previous versions of execline and skalibs. Has anyone encountered this too? Already fixed in skalibs-2.10.0.1 ;) (I generally don't make announcements for bugfixes releases, maybe I should.) Also, not related to above, the trap.html documentation page contains some typos: "multisusbstitute" at the second point of the "Notes" section and possibly "will be still be caught" at the "Options" section. Thanks, will fix. -- Laurent
"emptyenv -c" unsets all environment variables
Hello everyone, I'm using skalibs-2.10.0.0 and execline-2.7.0.0 here in my system. I noticed on my system that "emptyenv -c" unsets all environment variables just like "emptyenv" does. This didn't happen with previous versions of execline and skalibs. Has anyone encountered this too? Also, not related to above, the trap.html documentation page contains some typos: "multisusbstitute" at the second point of the "Notes" section and possibly "will be still be caught" at the "Options" section. Thanks!
Re: multidefine chomps a non-delimiter character(s)
Got it. Thanks! On Thu, Feb 13, 2020, 4:54 PM Laurent Bercot wrote: > Based on my understanding, it should output "foo bar1 bar2". But instead > of that, the output is just "foo bar1 " (notice the space after bar1) so it > seems that bar2 is being chomped, leaving $c with an empty word. Is this > the intended behaviour? > > > It is intended. From > https://skarnet.org/software/execline/el_transform.html : > > < The last sequence of characters in the value will be recognized as a word > < even if it is not terminated by a delimiter, unless you have requested > < chomping and there was no delimiter at the end of the value before the > < chomp operation - in which case that last sequence will not appear at > all. > > Unless you know your value ends with a delimiter (so, a space or a tab), > don't use the -n option to multidefine. > > -- > Laurent > >
