ZH $ sudo systemctl stop acpid
ZH Job for acpid.service canceled.
... because, as noted, it's a socket-activated service, which actually
makes it two separately startable and stoppable things
(acpid.service and acpid.socket) in the world of systemd, only one
of which is being stopped when you're
Cam Hutchison:
I've been using runit for some time, which is a clone of daemontools
runit is not a clone of daemontools. s6
(http://skarnet.org/software/s6/) is much like daemontools, with some
extensions. It has the s6-svscan, s6-svscanctl, s6-supervise, s6-svc,
s6-svok, s6-svstat,
Jonathan Dowland:
You need to write a .service file for your svscanboot script, and
put it in /etc/systemd/user.
I did systemd units for this ages ago. It's better to do this as two
units: a path unit that watches the service directory and a
service unit that is started when the service
T.J. Duchene:
Why is it not possible to create a completely generic shell script -
basically ala SysV that can parse systemd config files for those use cases
where Systemd is undesirable?
Your question takes a falsehood as its premise. It is far from
impossible to parse .INI files with
Hans Ullrich:
However, everything is working well, as far as I see.
Maybe it is, because I am using encrypted filesystems? Or because of using a
SSD-drive?
Look; don't guess. You've discovered with systemctl list-units
--failed which units have failed. Now use systemctl status on each of
Hans Ullrich:
I do not understand the policy behind systemd. As far as I know, It
is historical in uinices, that each folder like /bin, /sbin, /var,
/usr etc. is residing on its own partition. This is from the time of
SCSI-drives (as you can have 16 drives on a controller).
Both of those
Andrei Popescu:
Why should I write a script? I'm not a programmer.
I can write a (simple) shellscript, but I wouldn't dare write an
initscript or even a daemontools runscript.
You have an incorrect mental model of the relative difficulty of the
tasks. A run program for a daemontools-family
Andrei Popescu:
I recently needed something to run imapfilter and restart it in case
it might exit, so I had a look at daemontools. I gave up quickly [...]
And here's how one can do it with the nosh package
(http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh.html).
I took
Steve Litt:
### RUN THE DAEMON ###
exec envuidgid slitt envdir ./env setuidgid slitt \
/d/at/python/littcron/littcron.py \
/d/at/python/littcron/crontab
Joel Rees:
man exec for clues to that, understand that littcron.py is Steve's
special cron (right, Steve?), and that he is setting
Jonathan Dowland:
Next step, adjust the daemon to depend on this. In my example,
transmission-daemon supplies a .service file in the package. Copy this to
/etc/systemd/system, and add a line (the line prefixed +):
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
wande...@fastmail.fm:
I have a similar lack of awareness and/or understanding about all of
the *kit packages / projects / tools / what-have-you, actually; I'm
not positive I even know how many there are, much less all of their
names.
This should help:
Put yourself in the position of
Rob Owens:
I'm not sure what is meant by nobody has taken ownership of the
'request for package' bug. If that's something that needs to be
done, tell me what is required and I'll see if I can do it.
It is Debian bug #763499, for reference.
--
To UNSUBSCRIBE, email to
Lee Winter:
One key component of an effective startup process is dependency
handling. So why not look for one of the best as a model? I
suggest DJB's redo system. It is excruciatingly simple. But very
effective. And it is the opposite of monolithic.
Is practically nonexistent the
Andrei Popescu:
Upstart was the only real contender to systemd at the time of the
evaluation by the Technical Committee, but it has or is being
replaced by systemd everywhere.
Tanstaafl:
And why was OPenRC not a contender?
Your question takes a falsehood as its premise. It actually
Ric Moore:
You have to make a concerted effort to enable systemd to Wheezy. I
mean, you really have to try hard. :)
It isn't that hard. But one does have to regularly type in a barefaced lie.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe.
Charles Kroeger:
I think it's ludicrous that adding an SD card that even has its own
line in /etc/fstab, throws the whole system into 'emergency' mode.
I see from other messages in this thread that I'm not the only person to
think it equally ludicrous to have a workflow that involves
The Wanderer:
If the mount failing isn't that critical, then the right way to fix
the problem under systemd's apparent design would probably be to add
the noauto label to the fstab, so that the device will not mount
automatically on boot.
Actually, that's just the widespread NON-systemd
Christian Seiler:
Finally: Upstart also supports socket activation. It's not quite as
powerful as systemd's, but is has enough features for this use case.
I don't know the people developing util-linux, but I could imagine
them accepting a patch to also support Upstart-style socket
Dimitrios Chr. Ioannidis:
A quick search reveals the following.
I've a software that use libuuid. Until now, the uuidd had the
ability to start on-demand the uuidd if the later, quotting ...
setuid to an unprivileged user (e.g. uuidd:uuidd).
After that commit, i'm forced to use systemd,
Martin Manns:
After switching to systemd, [...] password entry on startup looks
weird because some weird red moving stars are shown instead of a
prompt. [...] This is probably a configuration issue. However, I was
not able to find a good solution with google (between all the systemd
Martin Manns:
After switching to systemd, I would like to get back the following
behavior: [...]
Martin Steigerwald:
In fstab in the column pass you can only specify the fsck order,
not the mount order.
No, he cannot even do that. He's switched to systemd, remember. systemd
converts
Laurent Bigonville:
The systemd umbrella project is made of 10+ different executables
that have all a specific scope (systemd PID1 used to manage the life
cycles of the daemons, systemd-logind manage the user sessions,
systemd-journald a logging system,...) and that are all
communicating
Jerry Stuckle:
But just the fact there are people who consider systemd to be
problematic enough to consider forking Debian should not be ignored.
Denis Roio already has dyne:bolic.
*
http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/run-scripts-and-service-units-side-by-side.html
Martin Manns:
Seriously, I doubt that any ordinary user finds this before
migration, i.e. when you do not have installed systemd, have you got
those man pages on your system?
That's a failing of Debian packaging in general, not specific to
systemd. Few packages have separate -doc or
Miles Fidelman:
I could be wrong, but it strikes me that the strongest voices for a
fork are coming from folks who run servers [...]
You are wrong. The strongest voice is coming from Denis Roio, who is
the person behind the WWW site that everyone is pointing to. And as I
just mentioned,
Psst! Listmaster! This was a false positive. M. Ullrich has actually
hit a genuine, and widely reported, bug in checkrootkit. Ironically,
that's a false positive too.
Hans Ullrich:
Searching for Suckitrootkit... Warning:
/sbin/init INFECTED
The file /sbin/init is a
Nate Bargmann:
Comparing the two systems I see that the one with the failure has
'console-kit-daemon.service' shown as active (running) and the one
without the failure shows it as inactive (dead). The consolekit
package is installed on each system, but '/etc/systemd/system'
doesn't have
Miles Fidelman:
Seriously, nowhere, in all the discussions of systemd, have I seen a
significant number of people - other than those directly or
indirectly associated with systemd - stand up and say we really,
really, need a new init system, [...]
Admittedly, my focus is server-side only,
Jonathan de Boyne Pollard:
Contrastingly, the people who were propounding OpenRC at the time
provided a good example of how NOT to go about doing so. Their
several mistakes are worth learning from.
Tanstaafl:
Not sure I understand what you are saying here...
Are you saying that some
Andrei Popescu:
Upstart was the only realcontender to systemd at the time of the
evaluation by the Technical Committee, but it has or is being
replaced by systemd everywhere.
Tanstaafl:
And why was OPenRC not acontender?
Jonathan de Boyne Pollard:
Your question takes a falsehood as its
Martin Read:
1. The init daemon should fork exactly once; in the child it should
exec another program, while the parent (PID 1) does nothing except
reap zombies.
2. As (1), except that if the initially-forked child process exits,
PID 1 should repeat the fork and exec-in-child procedure.
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
Gary Roach:
I found some script for rsync to write rsyincd.socket
andrsyncd.service and put them in /lib/systemd/system directory.
That was wrong. Locally made, non-packaged, unit files belong in
/etc/systemd/system/ . /lib/systemd/ is the province of
package-controlled stuff, which your
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
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
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
Brian:
Systemd handles the terminals [...]
... and all of the mucking around that you two and participants in some
other Debian bugs are doing, laudable as it is, is to tweak something
that is in fact already superseded by TTYVTDisallocate=yes in
autovt@.service . (-:
August Karlstrom:
Stuart Longland:
I've used the OpenVPN init script as a template for creating my init
scripts, [...]
And that's the point at which you went wrong. OpenVPN was one of the
earliest things converted to systemd with its service management set up
very differently to the way that its previous
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
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
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
*
The Wanderer:
Some people develop and distribute malware as free software. Do they deserve to
be treated with respect for doing that?
I strongly suspect that malwares do not provide freedoms #1, #2, or #3
out of the Four Freedoms.
T.J. Duchene:
One programmer created asystemd fork called "uselessd".
He declared it dead about six months ago.
The Wanderer:
Also on a mostly-cosmetic level, if you log in at a text console
without systemd, you will get a certain set of messages, coming mostly
from login and from your shell - but with systemd, logging in at a
text console also produces a mess of extra messages coming from
logind,
Christian Seiler:
Note that _nobody_ working on su, neither upstream nor maintaining it
in distributions, has claimed that they will stop.
Indeed. The implication that su is being replaced has, rather, come
from the technology journalists and web log diarists writing headlines ...
* Paul
Charlie Kravetz:
There has never been mention of any other method to exit this new
shell command.
Probably because the people knowledgeble in the subject thought that it
went without saying. It plainly doesn't, because this is the third
place where the whole
Lennart Poettering
(https://github.com/systemd/systemd/issues/825#issuecomment-127917622):
Long story short: su is really a broken concept.
Christian Seiler:
So it's not like su is suddenly broken - it's just that some specific
new use cases don't work properly with it.
A fair
The Wanderer:
No, but I believe I still have my laptop configured in a way which
gets this behavior. If you want, I can reboot it and do a detailed
examination; I'm probably about due for a reboot of that laptop, anyway.
It's mainly the final part about other people's login sessions
"David" :
I'm not familiar with why sysvinit was a problem
*
http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/system-5-rc-problems.html
You're late.
T.J. Duchene:
If someone can do it better, and still keep it compatible with POSIX,
more power to them.
This is not the first place where someone has randomly thrown POSIX into
the discussion. "su" is outwith the scope of the POSIX standard. It's
in the SVID, but to my knowledge "su"
Doug McGarrett:
The last time I looked--about 6 months ago--FreeBSD requires a
filesystem that is not compatible with Linux or Windows; nothing
cancommunicate with it.
About six months ago, FreeBSD could still perfectly happily run on UFS
volumes, and there was no such requirement. I am
The Wanderer:
there are plenty of hits explaining how to make systemd inhibit
shutdown or add a delay or the like, and a few hits related to Debian
bug 635777 (which seems to be about a delay after the shutdown has
actually begun, not about a delay in initiating the shutdown), but no
real
David Wright:
I think the arguments have changed/been juggled/reduced. The lack of
-F is especially annoying.
They haven't been. All of the documented options to upstart's shutdown
command and the System 5 rc shutdown command are recognized, albeit that
four of them, including -F, are
The Wanderer:
It's still odd / bothersome that systemd's shutdown would see the
unsupported / unrecognized '-t' option and just proceed blithely
along, rather than erroring out on the presumption that a mistake may
have been made.
It's an engineering choice, to not break existing scripts
Ralph Katz:
There is no "-t" option.
In fact there is. It's undocumented; and is one of four undocumented
compatibility options, alongside -a, -f, and -F, that are simply parsed
and then ignored. There is a fifth undocumented option with an effect, -K.
The Wanderer:
I can certainly see the reasoning, though I'm not sure I wouldn't have
come down on the other side of that decision.
I actually have done myself, on occasion.
The Wanderer:
Wouldn't it at least make sense to print a message to the effect of
"warning, ignoring unsupported
Ralph Katz:
There is no "-t" option.
Jonathan de Boyne Pollard:
In fact there is. It's undocumented; and is one of four undocumented > compatibility options, alongside -a, -f, and -F, that are simply >
parsed and then ignored. There is a fifth undocumented option with
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
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.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.
*
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
BAGI Ákos: > I set up on jessie my own dns server with tinydns. > Whow
to set up /etc/networking/interfaces and resolv.conf to ask the system
for my zones himself first?
The people who are telling you to "run tinydns in recursive mode" don't
know tinydns at all, as they did say. What
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
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
update-rc.d my-program defaults 20 80
update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .
Support for run levels in "start" and "stop" subcommands was dropped
from update-rc.d by Roger Leigh in 2013. You'll find that the command
has been warning you about using explicit run
Looks like systemd does not execute the statements in status) case of the init script
at all, but just checks if the daemon process exists. My '/etc/init.d/ status' did much more, i.e., it checked if the daemon was actually able to
do some real work.
So far I have had no luck in finding the
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,
Felix Miata:
Only with that one particular URL.
... which is officially recognized.
* https://debian.org/News/weekly/2013/19/index.en.html#manpages
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
**
Michael Biebl:
There are 3 kind of "timestamps":
Access - the last time the file was read
Modify - the last time the file was modified (content has been modified)
Change - the last time meta data of the file was changed (e.g. permissions)
Not on all flavours of Debian. Debian FreeBSD has
Michael Biebl: > Strictly speaking, the tmpfiles.d mechanism is not tied
to a particular init. It's just that no-one has provided an
implementation for non-systemd.
Untrue. The OpenRC people have had a tmpfiles utility since 2012.
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
Jonathan de Boyne Pollard:
Untrue. The OpenRC people have had a tmpfiles utility since 2012.
Michael Biebl:
I didn't know that. Thanks for the info.
Can you post some more details? Where can I find the sources for that?
Is it packaged for Debian?
Here's the Gentoo OpenRC repository
Andrew M.A. Cater:
/etc/os-release just contains major version
You are going to have to explain that to its manual page, which gives
VERSION_ID=11.04 as an example of what can be in the file.
You're going to have to explain it to the Ubuntu people, as well;
because they follow what the
André Majorel:
Do you think the following would work on any Debian system, regardless
of its current run level and choice of init system ?
1. run invoke-rc.d daemon-package stop
2. update config file
3. run invoke-rc.d daemon-package start
Don't use invoke-rc.d yourself. The *old
The nosh package is now up to version 1.32 .
* 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/
This release fixes two problems with Gentoo Linux (control group version
detection and a
Mattia Oss:
This can be seen in the 3rd video.
Lisi Reisz:
By you. Not by me - nor apparently by Felix.
It's really simple. It's the same size monitor. The "normal"
characters are high resolution 24-bit colour graphics mode with 8*16
pixel glyphs, giving 240 columns by 67 rows. The
Felix Miata:
At what point exactly within either of those videos does 80 by 25
appear? All I saw anywhere appeared to be in the vicinity of 240 by 67.
I think that I have put my finger on the source of your perplexity.
Remember where M. Oss said the following?
Mattia Oss:
This can be
Someone:
I haven't installed much else yet on the system but I tried the
sysstat package which gives me the following error:
preset: ERROR: sysstat: No such file or directory
I haven't yet investigated this problem. Sysstat seems to be part of
the Debconf enable/disable system, I'm
Joe:
Using strings /var/log/journal/*/* | grep debian-kernel [...]
Or one could just use journalctl .
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
- the absolute need for
minor version is small.
Jonathan de Boyne Pollard:
You are going to have to explain that to its manual page, which gives
VERSION_ID=11.04 as an example of what can be in the file.
Pascal Hambourg:
This is obviously not a Debian version. Rather looks like Ubuntu
Rainer Dorsch:
[ 20.704584] systemd[1]: Initializing machine ID from D-Bus machine ID.
[ 20.916182] systemd-journald[2136]: Failed to open runtime journal:
Invalid argument
You need to look at at least two files, /var/lib/dbus/machine-id and
/etc/machine-id . They should contain only a
Rainer Dorsch:
But to my surprise even on a fresh install of the jessie image
/etc/machine-id is already broken:
root@scw-790923:~# cat /etc/machine-id
9d1b906dd5ea40359e2071d29c12aabe
71f
root@scw-790923:~#
But it seems the systemd version in jessie seems to be more tolerant
against
The nosh package is now up to version 1.31 .
* 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/
This release fixes a problem with emergency mode that was introduced by
accident in 1.29 .
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
*
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
Anonymous:
The error message:"A start job is running for LSB: Raise
network interface (xx sec/no limit)". Where xx is a count up in
seconds that never ends.
Greg Wooledge:
"LSB" stands for Linux Standard Base [...] I don't know what LSB has
to do with Debian's boot process waiting for
Joe:
A fair number of wheezy systems will be servers, upgraded many times.
Mine started out as sarge. What are the odds of such a system making
the change to systemd without problems?
It depends. But my own experience is that *if they were already using
systemd* on Debian 7, it was a
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
Greg Wooledge:
Neither of those links talks about jessie's specific default script that waits
for network interfaces to start.
They do, however, explain what LSB has to do with things, which was what you
wondered about.
Greg Wooledge:
Neither do they mention this "van Smoorenburg".
Rainer Dorsch:
> I think this then results in errors during an apt-get upgrade:
It does indeed. It is systemd-journald that resides at the server end
of /dev/log on a systemd operating system. Quite a lot of other stuff
will break for you if you don't have a running systemd-journald,
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
The nosh package is now up to version 1.30 .
* 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/
service bundles
---
As usual, there are more service bundles, including for the
djbwares is now at version 5.
* http://jdebp.eu./Softwares/djbwares/
* http://jdebp.info./Softwares/djbwares/
This contains some long-overdue changes: ip6.int has been replaced by ip6.arpa
in tinydns-data and dnscache, and rblsmtpd no longer falls back to using an RBL
that has been defunct for
The nosh package is now up to version 1.33 .
* 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/
This has been held back because of work being done by someone else. I don't
want to steal xyr
Greg Wooledge:
>
> Suppose you want to start DJB's daemontools from a locally created systemd
> unit/service. Here's a file that will do that:
>
... albeit poorly. If one wants to run daemontools under systemd, svscanboot is
not the way; svscanboot is a thing of the past
Dan Ritter:
>
> Eventually we'll have to do the work, but the operations staff here has a
> consensus that if we're going to do the work, we might as well go to a system
> that we feel capable of understanding and trusting, something more like
> daemontools. Nosh is being considered.
>
Nicolas George:
> The process with PID one is the only immortal process on the system, and
> adopts all orphan processes.
Wrong. Indeed, it was the systemd people who drove the making it wrong.
* https://unix.stackexchange.com/a/177361/5132
Daniel Pocock:
> Do any of the mailers (postfix, exim, etc) provide a convenient way
> to exclude delivery to system accounts by default, or to exclude
> these aliases and accounts from receiving mail from external senders?
> Could anybody share examples of how they do it or pointers to
> any
1 - 100 of 166 matches
Mail list logo