Luke Diamand:
> Are there any plans to create a debian package that would just put all
> the bits in the right place, so you can simply install the package and
> have it then use runit-init as /sbin/init ?
It's called runit-run, created over a decade ago, and it was a Debian
package for some yea
Avery Payne:
> * implement a ./wants directory. [...]
> * implement a ./needs directory. [...]
> * implement a ./conflicts directory. [...]
Well this looks familiar.
Before you read further, including to my next message, get yourself a
copy of nosh and read the manual pages therein for servi
Avery Payne:
But from a practical perspective there isn't anything right now that
handles
dependencies at a global level.
Now you know that there is.
The nosh design is, as you have seen, one that separates policy and
mechanism. The service-manager provides a way of loading and unloading
Avery Payne:
I have been giving the "one shot" question considerable thought. I
have a
number of scripts that require this kind of behavior, so it's of great
interest to me. The current methods that I have encountered are:
+ use a pause(1) command that simply sleeps forever on a subset of
s
John Albietz:
> I wonder if this will help address a common situation for me where I
> install a package and realize that at the end of the installation the
> daemon is started using upstart or sysv.
>
> At that point, to 'supervise' the app, I first have to stop the current
> daemon and the
Avery Payne:
Finally, with regard to the up vs actually running issue, I'm not even
going to try and address it due to the race conditions involved.
RabbitMQ is the canonical example of the real world problems here. With
durable queues containing a lot of persistent messages, it can be tens
o
Laurent Bercot:
I'm of the opinion that packagers will naturally go towards what gives
them the less work, and the reason why supervision frameworks have
trouble
getting in is that they require different scripting and organization, so
supporting them would give packagers a lot of work; whereas
Laurent Bercot:
Readiness notification is hard: it needs support from the daemon
itself, and most daemons are not written that way.
Ah yes. That reminds me. I said a while back that I have to give some
of you some good news.
https://lists.debian.org/debian-devel/2014/10/msg00709.html
nosh is now up to version 1.14
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
These particular changelog entries are a big deal for Debian Linux.
* The previous regular sockets, sysinit services, and standard
targets packages are now all merged into the bundles p
Wayne Marshall:
Under a supervision framework, failure of a service starting is absolutely ok.
(Many novices fail to grasp the elegance of this essential feature.)
... and novices and non-novices alike fail to grasp its unscalability.
It may be fine on a hobbyist PC, but on a server in a da
Buck Evan:
For example, I'd like to encode the fact that I don't expect service A to be
able to come up before service B.
In nosh, the filesystem is the database. This is an ordering, not a
dependency. One can separately encode in nosh (a) that start of service
B will cause the start of se
Avery Payne:
There's already a project for adding definitions for various daemons.
http://bitbucket.org/avery_payne/supervision-scripts
There are even more than that. I mentioned back in January that the
nosh Guide chapter on creating service bundles has pointers to the run
file collections
An anonymous person has a problem with runit under upstart on Ubuntu
Linux version 14: http://askubuntu.com/questions/630166/
So too do others on the hyperlinked Launchpad bug discussion. You might
like to help them all.
nosh is now up to version 1.16
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
As you'll see, the WWW pages have expanded a bit. In part this is
because of the Big News, which is the arrival of FreeBSD packages,
bringing FreeBSD up to par with Debian. The old box
Guess who didn't spot that it was Cc:ed to a mailing list? (-:
Some of the salient points that others may be interested in from what I
sent privately, plus some extra general-audience stuff:
Yes, kqueue. Being in the very first bullet point right along with the
other important API dependenc
Avery Payne:
I need to think through a kernel-neutral method of handling driver
loading. There are a handful of services that require this to
succesfully launch. For example, cpufreqd requires kernel modules to
load first, but this is linux-specific. Does FreeBSD have any
requirements like
James Powell:
If runit had the ability to order processes like OpenRC where you have:
before=
after=
setups, you could order the entire tree structure.
As I might have mentioned before, people have been saying that one could
do that for years; nosh is the existence proof that it can be done,
James Powell:
For some comic relief:
> "We are systemd. You will be assimilated. Your projects and software
> will be deprecated, reinvented, and added into our own, and made to
> service us. Resistance is futile." -Lenncutus of Borg.
I don't really agree with all of the nonsense that surrounds
post-sysv:
Of course, your particular example would be made less gruesome simply
by introducing a rate limit on startup failures. This strategy seems
to be employed frequently in launchd setups.
It's a standard daemontools thing, also. It's hardwired into the
original "supervise".
I had to
post-sysv:
Readiness protocols require application-specific integration, do they
not? Even if it's something as simple as writing to a FIFO.
That is, of course, part of the problem of readiness protocols that I've
been telling people about.
(https://lists.debian.org/debian-devel/2014/10/msg00
Laurent Bercot:
What is true for datacenters even more than for hobbyist PCs, however,
is that you definitely do not want cascading failure. And instant
restart is a recipe for cascading failure: if your dnscache cannot
start for some reason and dies instantly, and your supervisor restarts
it
Laurent Bercot:
Jonathan de Boyne Pollard:
Application X, whose rate of continual DNS lookups is why there's a
local dnscache in the first place, needs as close to uninterrrupted
DNS service as it can get, even in the face of system administrators
who know that "we can just clear th
post-sysv:
I still remain convinced that crash-only software was a key insight of
Erlang, engineering systems so that restarts to a known good state is
feasible in of itself because components are discrete and trying to
intervene on internal program state becomes an exponential nightmare.
As
Avery Payne wrote:
I suspect that you and Laurent would argue that I shouldn't be using
sockets inside of ./run as it is, [...]
I don't really understand this whole explanation of your problem, at
first blush. So I'm reserving any judgement. But ...
Avery Payne wrote:
If you have sequenced
Laurent Bercot wrote:
If all this fuss is about socket activation, then you can simply
forget it altogether. Jonathan was simply mentioning socket activation
as an alternative to real dependency management, as in "that's what
some people do". I don't think he implied it was a good idea. Only
L
redo is now at version 1.2
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/redo.html
Two changes. First, as you can see, there's now a pre-built FreeBSD
binary package.
The second change is something that has been annoying me for some
while. Sometimes, especially when one
nosh is now up to version 1.17
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
As I said to gdiazhartusch a while back, and as listed on the roadmap
page, there is now a tool for auto-creating the mount@*, fsck@*,
ttylogin@*, dump@*, and swap@* service bundles from
Jonathan de Boyne Pollard:
There's the steady chipping away at that list of 157 rc.d scripts,
which has just lost off its list a few pf services and savecore
amongst other things.
Yet another bug report that has come out of this is that the pflogd(8)
manual page has some gibberish unde
Just to let you know: This sort of feedback is much appreciated. I'm
not ignoring you. But I'm working completely mad hours at the moment
(over 67 hours during the past 5 days) and my time is somewhat limited.
Some very quick things to be going on with:
If there's a SIGABRT there should be some error output saying why. 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.
Having the bundle directory a direct su
Guillermo:
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.
[...]
a read() call on the file descriptor returned by the inotify_init() that
produces an EI
Guillermo:
Have you ever considered just writing a BSD backend using kqueue /
kevent, and a Linux backend using epoll / inotify or whatever native
Linux mechanism is available to suit nosh's needs? I believe you
mentioned there's quite a few conditional compilation already to work
around libkq
Georgi Chorbadzhiyski :
I don't want to overwhelm our admin team with notices on every service
restart (we are managing thousands of servers). I need a notice only
if the service restarts more than X times in a minute, which is a sign
that something is most definitely wrong. I'll have to hack s
nosh is now up to version 1.18
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
The big news for this release is the nosh-run-system-manager Debian
binary package. This, and the new additional service bundles in
nosh-bundles, package up everything that is needed for
nosh is now up to version 1.19
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
The important news is that the embarrassment with the post-install setup
script for the Linux nosh-run-kernel-vt package is fixed. It was a
missing 1-line escape() shell function. I apo
Guillermo:
Colin Booth:
As it stands, nosh is playing in the same space as upstart, launchd, and
systemd.
If you don't look too closely, you could also say nosh without the userspace
terminal and login services stuff more or less covers the same ground as s6,
s6-rc and a small subset of exec
Colin Booth:
I mean't more in the "one stop low-level system management" sense.
Also in the design of the nosh unit files (which may be a case of
parallel evolution, my knowledge of the history of nosh is limited at
best). Pholosophicaly it's definitely coming from the daemontools world.
Yes
Colin Booth:
The distinction is specifically thus: ./up is what fires when the
service is brought up, ./down is what fires when the service is
brought down, ./run is what fires when a non-running service is
supposed to be running, and ./finish is when a running service stops.
Just because one
Guillermo:
Hi, I had some issues with the source package I thought I should mention:
As I said I intended to a while back, I incorporated fixes for these
into version 1.20. This is now out.
Laurent Bercot:
s6-rc is a service manager for Unix systems, running on top of a s6
supervision tree.
... which according to https://news.ycombinator.com/item?id=10277123 is
configured using proprietary binary blobs.
The nosh package is now up to version 1.20 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
It's worth noting that the WWW site has gained some more pages, an
installation how-to and a quick look at user-space virtual terminals.
*
http://homepage.ntlworld.com./jo
Joe Maloney:
do you have a source code repository somewhere for nosh?
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/source-package.html
The source package and how to build from source are here.
The nosh package is now up to version 1.21 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
console-terminal-emulator now has a mouse input event protocol, and
speaks both the DEC VT Locator protocol and the xterm Private Mode 1006
protocol over the terminal interf
The nosh package is now up to version 1.22 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
There are several things in this release:
* a new binary package for FreeBSD
* improvemen
On 2015-11-05 01:29, Guillermo wrote:
So problem solved. Thank you, this is a major improvement.
Brill. Thank you for the confirmation.
The nosh package is now up to version 1.23 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
There is one major item in this release.
* I've adjusted console-fb-realizer's keyboard h
Guillermo:
It seems that the 'unload-when-stopped' and 'version' subcommands of
system-control are not mentioned in the documentation.
They both should be. I've added the latter to the doco ready for the
next version. The former I'm wavering about. I've had a to-do item for
some time to t
Guillermo:
So I looked at the source/targets/virtualbox-host.target file from
which the bundle is created, and, IMHO, there are some issues with it.
That's not surprising. Running as a virtualbox host is not something
that is well tested. As you can see from the roadmap WWW page, there
are
The nosh package is now up to version 1.24 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
Minor items in this release include:
* A fix for BSD keyboard layout import, that makes b
Olivier Brunel:
With instanced services, it means when you enable such a service you
add/specify an instance name. So e.g. the servicedir is "getty@" but
you enable "getty@tty2" -- which just means the servicedir getty@ is
copied under a different name in the scandir.
The intent being that t
Laurent Bercot:
You can't supervise a pipeline per se; you need to supervise both
processes in the pipeline independently, and make sure the pipe isn't
broken when one of them dies.
So, have "exec inotifywait /dev/disk" as foobar/run, and have "exec
automounter.py" as foobar/log/run. This wi
I was going to warn you that you're about to kick yourself, but I see
that Guillermo has already replied, so you're probably already kicking
yourself. (-:
fREW Schmidt:
First off, there's no README or anything, so I sorta have to guess.
[...] Again there's no README for redo.
As Guillerm
It might be worth asking what
* http://lua-users.org/lists/lua-l/2006-10/msg00770.html
was all about.
See also:
* https://dev.openwrt.org/ticket/8453
* http://people.igalia.com/aperez/bill/lib/www/http.html
*
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg02065.html
The nosh package is now up to version 1.25 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
As you may have noticed from discussions elsewhere, a new
oom-kill-protect utility has sn
fREW Schmidt:
To read the docs check out
https://github.com/frioux/cgid/releases/download/v0.1.0/cgid-v0.1.0,
where you can see examples of how to run under `nosh` or `s6`.
That URL returned an XML error document from Amazon to me.
https://github.com/frioux/cgid/releases/tag/v0.1.0 was a
The nosh package is now up to version 1.27 .
* http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
In fact, it is soon to be version 1.28. This is a somewhat delayed
notice for 1.27, beca
Ubuntu 15 and 16 have both systemd and ubuntu installed. This causes
problems, and has been causing for over a year. Yes, all of these are
the same core problem:
* http://unix.stackexchange.com/a/284453/5132
* https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164
* https://bugs.launc
I have an application for which I need to keep all logs indefinitely.
Rotating them into sub-directories would help keep the number of files
from expanding into an unmanageable number. So if someone has any
other suggestions on how to manage log rotation without pruning, I'm
all ears.
So wh
IMHO more "proper" or rather interesting approach, could perhaps be
some kind of helper program - "injecting" "alternator" sub-process -
which would be running under s6-supervise.
The haproxy people have already done this work for you. They call the
program haproxy-systemd-wrapper. It's undo
it looks like chpst cannot currently (or never could, not sure) change
hard limits.
The limit stanza in an upstart job file sets both hard and soft limits,
explicitly.
* http://upstart.ubuntu.com./cookbook/#limit
* http://smarden.org/runit/useinit.html#upstart
Bernstein's original softlimit
Guillermo:
So, the convert-systemd-units tool recognizes the systemd 'StandardInput=tty'
unit file directive, and translates it to a vc-get-tty + open-controlling-tty
sequence in the 'run' file of the generated bundle directory. Which does more
than just redirecting stdin to the appropriate ch
Guillermo:
And as a consequence, the Guide ends up never actually explaining what
the unload-when-stopped subcommand does (AFAICS, make service-manager
unload the named service after its 'stop' file finishes executing,
whatever the reason for running it was, so that a subsequent
service-status
Christophe-Marie Duquesne:
Any idea how to proceed?
You're running a daemon. It really shouldn't have an interactive user
interface. Remember the lessons that resulted in Session 0 Isolation in
Windows NT.
There are several poor approaches. Here are two more:
* Make your password into c
Jonathan de Boyne Pollard:
1.28 is pretty much frozen now, and its release is awaiting my writing
a WWW page about the MySQL/MariaDB changes. Enjoy a peek at one of
the new pages already written:
*
http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/italics-in-manuals.html
Laurent Bercot:
for logdir in `cat logdir_list` ; do (cd $logdir && cat *.s *.u
current) ; done | sort > logfile
find `cat logdir_list` -maxdepth 1 -type f \( -name '*.[su]' -o -name
current \) -print0|xargs -0 sort -m -- > logfile
sort can do a merge sort directly from the original files
Vincent de RIBOU:
Is it possible to perform the same mechanism but having concatenated
file along all the others at all times ?
There's always tail with the -F option on a list of "current" files.
But you're then limited to just the "current" log data, it's tricky to
track which output co
Pierre Jacomet:
I did a couple of fixes to the debian package installer such that the
debian/ubuntu installer deals properly with the dichotomy between
systemd and upstart and the fact that they both may be installed in
the system at the same time. This was causing the installer to fail in
ub
The whole sorry tale of why is on the new WWW site. The upshot of it is
that nosh and redo are in a new place.
* https://jdebp.eu./Softwares/nosh/
** https://jdebp.eu./Softwares/nosh/source-package.html
** https://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html
** https://jdebp.eu./Sof
The nosh package is now up to version 1.28 .
* https://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/
There's a lot in this one: MySQL and MariaDB changes; more prophylaxis
for Desktop Bus bus a
Guillermo:
Clicking on the links to the *.bz2 source packages results in an HTTP
404 error (but not with the links to the *.gz ones, so the packages
can still be downloaded). The same thing happens with the links about
their slashpackage-style, which point to a nonexistent FGA (I don't
remembe
Guillermo:
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 the chicken-and-egg
situation we had with nosh-1.19:
It was supposed to be that way already.
>
> I'm going to be very naughty and patch 1.28 post-release. It's a minor
> change.
>
I've changed my mind. I'm going to point the two of you at a potential version
1.29 and see how you get on.
This is because I have ended up doing slightly more than a 2-line script patch.
Guillermo:
OpenBSD
===
[...]
There are an awful lot of limitations to OpenBSD, [...]
How funny it is that this summary and the WWW page echo the sentiments
in skarnet.org packages' source files comments and commit messages :D
We didn't collaborate. (-: I don't actually know what M.
I don't know why you asked about FreeBSD rc.d just on the Debian mailing
list; but I'm going to deal in both of those and others besides, here,
and things that apply across both, so I've re-included the FreeBSD
mailing list. (-:
2016-08-14 15:10, Julian Elischer:
I don't know if I just misse
Guillermo:
> a) SIGTERM for reboot
> b) SIGUSR1 for halt
> c) SIGUSR2 for poweroff
> d) SIGINT for a programmable CTRL + ALT + Del action
> e) SIGWINCH for a programmable 'keyboard request' action
>
> nosh's system-manager supports e) via the 'kbrequest' target. But for
> compatibility reasons, su
http://adrianchadd.blogspot.co.uk/2016/08/freebsd-on-tiny-system-whats-missing.html?showComment=1471236502051#c1305086913155850955
, Adrian Chadd:
We're using s6 at work, and it works out mostly ok. Mostly once you
get around the linuxisms, and the lack of sensible time code in it
(its calcula
Jonathan de Boyne Pollard:
What are these Linuxisms in s6? s6-linux-utils and s6-linux-init have
Linuxisms, obviously. But what Linuxisms does s6 have?
Adrian Chadd:
We just had a bunch of fun trying to get it to build right, [...]
Such as what, specifically?
Adrian Chadd:
Sure, but I'm looking for something more generic than just devd. Like,
notifications about events like "default route is up" can be done by
sniffing the rtsock, but notifications like "ntpdate has updated the
date, we can now do crypto services" doesn't happen there right now.
Adrian Chadd:
[...] the uptime stuff really threw us.
It's unfair to lay such system time problems at s6's door. Systems whose
system clock jumps 46 years during system bootstrap don't get to blame
s6 for mad time gaps that appear in logs and service start time
records. There is a *lot* of
Gerrit Pape:
To me too this readiness IPC ideas and implementations look
over-engineered.
A good convention for service programs would be to functionally test
for services it needs very early on startup, and fail if dependencies
are not available. The service supervisor (any modern init sche
Simon McVittie:
This can already work. If you put XDG_RUNTIME_DIR in user programs'
environment, and arrange for your favourite service manager to make a
dbus-daemon (or something else that speaks the same protocol) listen
on $XDG_RUNTIME_DIR/bus before any user process would try to connect
t
Just so everyone knows. This didn't get ignored. Guillermo has been
quietly playing with 1.29 behind the scenes.
This was a mixture of things. 1.29 will have (already has) some fixes
for the genuine bugs and for some of the things which are the subject of
much debate. (-:
The fprintf()s
Daniel Kahn Gillmor wrote:
So i'm hoping that it'll find a taker in one of these more
toolkit-style supervisor suites.
http://jdebp.eu./Softwares/nosh/#Features
socket services section
Daniel Kahn Gillmor:
#!/bin/sh
mkdir -p /run/kresd/workdir && \
setfacl -m u:kresd:rwx /run/kresd/workdir && \
cd /run/kresd/workdir && \
exec listen -udp::53 \
-tcp::53 \
-tcp:label=tls:853 \
-unix:label=control,mode=06
Laurent Bercot:
how does the daemon know what fd corresponds to what use?
In the wild, it's generally a for() loop over the passed-in descriptors
that checks each socket type. In the wild, only one of any type is
often the case.
"If AF_INET4 and SOCK_DGRAM, this must be my UDP4 socket."
T
Laurent Bercot:
fds 6 and 7 are only used for UCSPI clients, which are a very minor
subset of the programs you'd want to use that mechanism with.
Laurent Bercot:
I don't want the caller to tell me "here's a bunch of fds, you sort
them out": that's just laziness.
Just so that everyone is
Colin Booth:
--system loads the system defaults.
Actually, it tells it that it is a system-wide broker rather than a
per-session or per-user broker.
Otheus:
From systemd's viewpoint, the *service *is runsvdir, and not
runsvdir-start. The latter is simply a wrapper script for the former
and needed because of initttab's limitations. With systemd, a service
file can contain all the information in that script and more.
Similarly: http://jd
Jan Olszak:
Command that fails:
s6-softlimit -c 1 pwd
# strace s6-softlimit -c 204800 pwd
...
prlimit64(0, RLIMIT_CORE, NULL, {rlim_cur=RLIM64_INFINITY,
rlim_max=RLIM64_INFINITY}) = 0
prlimit64(0, RLIMIT_CORE, {rlim_cur=200*1024, rlim_max=RLIM64_INFINITY}, NULL)
= 0
You seem to have
The perp WWW site seems to have endured some damage. For example:
* http://b0llix.net/perp/site.cgi?page=tinylog.8 is truncated partway
through.
* http://b0llix.net/perp/site.cgi?page=perpd.8 is similarly truncated.
* http://b0llix.net/perp/site.cgi?page=links has some malformed markup.
Jean Louis:
emacs --new-daemon=NAME
I have added a new per-user service for this to nosh, ready for version
1.30 . So one just has to start the per-user service manager
# system-control start user@jlouis.target
then start the emacs server
$ system-control --user start emacs
Adj
The nosh package is now up to version 1.29. *
http://jdebp.eu./Softwares/nosh/ *
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.info./Softwares/nosh/ There's been a lot going on since
version 1.28 . 2016 leap second The TAI to UT
Bloody Thunderbird! Here's that again, I hope without the surprise
reformatting after pressing "send" this time:
The nosh package is now up to version 1.29.
* http://jdebp.eu./Softwares/nosh/
*
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project
* http://jdebp.in
Casper Ti. Vector:
one example for ulimit
An irony here is that the page *already contains* two entire sets of
examples that set memory resource limits, using daemontools,
daemontools-encore, freedt, perp, s6, and nosh tools.
In celebration of the forthcoming leap second, djbwares is now at version 4.
* http://jdebp.eu./Softwares/djbwares/
* http://jdebp.info./Softwares/djbwares/
I've added in the rest of M. Bernstein's public domain libtai library,
parts of which were already included by some of the tools. This ha
Casper Ti. Vector:
the docs are in tarballs on jdebp.eu
* http://jdebp.eu./Softwares/nosh/guide.html
Martin "eto" Misuth:
First, there are two major caveats,
There are actually three. They break scripting. For example: People
cannot use the GNOME Editor as $VISUAL or $EDITOR because one of the
things implicit in the $EDITOR/$VISUAL mechanism is that when the
program that has been invoked
Jonathan de Boyne Pollard:
In celebration of the forthcoming leap second, djbwares is now at
version 4.
* http://jdebp.eu./Softwares/djbwares/
* http://jdebp.info./Softwares/djbwares/
Jean Louis:
http://jdebp.info./Softwares/djbwares
is not working: "access denied" and I ins
Martin "eto" Misuth:
- rxvt-unicode - uberterminal
- this thing can operate [...] daemon, when single process hosts all your
terminals
- benefits are [...]
Drawbacks are that it doesn't understand receiving the listening socket
as an already-open file descriptor, and by default it p
Casper Ti. Vector:
But I do think the capability argument has its validity: chainloading
is, at this time, not well known to normal users, which is why many
systemd supporters compulsorily identify cgroup support with systemd
with few people opposing. Therefore I suggest to add some examples o
1 - 100 of 243 matches
Mail list logo
