Kenneth Porter:
OTOH, most of us learned from reading the writings of others in the
industry. So perhaps the wisdom of this thread should get captured in
a blog post by a security expert so it can be shared around on
multiple mailing lists and forums.
One can learn from the example of Daniel
Mantas Mikulėnas:
Maybe socket-activation would work for you? (With Nginx it's also a
hack though.)
Accept=No
Environment=NGINX=3;
It is not terrifically complex. The documented way to stop the forking
is "daemon off", but an inherited listening socket also does it.
* https://bugs.debian.o
st...@goodey.org:
[Service]
Type=forking
Your program has an -f option to stop it from vainly trying to
re-daemonize itself. Use it; and do not use Type=forking in the first
place.
*
http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html#DoNotBackgroundise
The supplied systemd
Cecil Westerhof:
Other services I can enable and disable.
And with chmod a-x /etc/init.d/tomcat8 you should
be able to disable this one, too. (-:
Read https://unix.stackexchange.com/a/394191/5132 for why.
Tom H:
The usual reason for not having a native unit is that you can't
force developers to do that work.
Psst! This discussion is predicated upon a falsehood. There is
an abundance of service units for Tomcat, and has been for years.
Lennart Poettering:
Uh, I am not sure what celery is, but if celery is started but exitson
its own then I am not sure I can help you very much.
Does it detach on its own? i.e. double fork? if yes, then type=forking
is the right choice, otherwise you need a different Type=.
A tip from one
Warner Losh, FreeBSD and embedded systems developer, has just invented a
new shutdowngoal, in addition to the ones that we already know. In
addition to the conventional reset, power off, halt, and kexec goals; xe
has added a power-off-and-then-on-again goal. Xe has named it power
cycle, and i
Reindl Harald:
> at least fall back to “nobody”
Jonathan de Boyne Pollard:
> That idea is wrong.
>
> https://news.ycombinator.com/item?id=14681377#14682059
Reindl Harald:
> better than a stupid [...]
Not really, no. It's the same category of error, in fact: substituting a
Reindl Harald:
>
> at least fall back to "nobody"
>
That idea is wrong.
https://news.ycombinator.com/item?id=14681377#14682059___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/system
"Igal @ Lucee.org" :
> Examples I see online use forking [...]
Jonathan de Boyne Pollard:
> ... because they are bad examples.
> Read http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
Andrei Borzenkov:
> Service type simple is the worst possible type as it d
"Igal @ Lucee.org" :
> Examples I see online use forking [...]
... because they are bad examples. Read
http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedeskto
Christian Rebischke:
> I would like to start ibus-daemon automatically on login in my user session.
The person who told you that this was unnecessary because ibus already has a way
to run the daemon via "bus activation" is wrong. There are various good reasons
to avoid bus activation, especially
Owens, Stephen:
The start script calls other scripts to start two application
components and then the start script exits.
One of the application components also spawns a couple of child processes.
There ends up being two pid files, one for each component, describing
the state of the applicat
Owens, Stephen:
UMask=0764
This is almost certainly wrong, by the way.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Reindl Harald:
earlier systems (sysvinit) hat no concept like emergency mode
This is a falsehood. Emergency mode was invented in December 1995,
ironically for that very system.
* http://jdebp.eu./FGA/emergency-and-rescue-mode-bootstrap.html
___
sy
Lennart Poettering:
"nofail" has been around as long as fstab has been around really.
This is a falsehood. /etc/fstab has a history that goes back to the
20th century. It was in UNIX System 5 Release 3, 4.2BSD, and OSF/1, for
examples. In contrast, the "nofail" option was invented in Dece
Benoit SCHMID:
echo -n "Starting Oracle Listener: "
su - $ORA_OWNR -c "env ORACLE_HOME=/oracle/XXX/12102
/oracle/XXX/12102/bin/lsnrctl start LISTENER_XXX"
Don't abuse su for dropping privileges.
* http://jdebp.eu./FGA/dont-abuse-su-for-dropping-privileges.html
It's now 201
I would like to start different processes in different ttys on boot,
What you need is a Q&A WWW site. (-:
* http://unix.stackexchange.com/questions/211544/
* http://askubuntu.com/questions/770673/
___
systemd-devel mailing list
systemd-devel@lists.fr
Avi Kivity:
We are using systemd to supervise our NoSQL database [...]
Sometimes [it needs] to perform expensive operations during startup
(log replay, rebuild from network replica) before we can start
serving. Rather than configure a huge start timeout, I'd prefer to
have the service report
Frank Steiner:
[...] I see such messages:
About to execute: /bin/echo -e 'Welcome to emergency mode! After logging in, ...
Forked /bin/echo as 4290
Failed at step CHDIR spawning /bin/echo: No such file or directory
[...] But |/usr/lib/systemd/system/emergency.service| contains:
[Service]
Dimitri John Ledkov: > Most filesystems support destructive operations,
with a goal to recover data via some-sort check/repair functionality
e.g. btrfs check/rescue, xfs_repair etc. > Some filesystems also require
periodic maintenance calls, e.g. something like the `harmless' fsck on
each mount
Daniel P. Berrange:
> Maybe it wasn't actually upstart, but one of the other init systems.
> I just recall getting a patch from Debian folks to support it via
> the /run/initctl path, rather than /dev, and assumed that was upstart
> related.
It wasn't upstart or one of the other init systems. It
dott...@gmail.com:
If systemd keeps going the way it does, it will eventually get forked,
[...]
Psst! This already happened, a year ago. Read
http://uselessd.darknedgy.net/ to learn what happened.
___
systemd-devel mailing list
systemd-devel
Fisher, Charles J.:
The xinetd server from previous versions of RedHat defined a REMOTE_IP
environment variable.
Lennart Poettering:
I wonder though whether it wouldn't be nicer to follow the variable naming used
by CGI here, and introduce $REMOTE_ADDR and $REMOTE_PORT instead of $REMOTE_IP
Lesley Kimmel:
I've been working with RHEL5/6 for the past several years and have
developed many init scripts/services which generally use lock files
and PID files to allow for tracking of the service status. We are
moving to RHEL7 (systemd) in the near future and I am looking for
instruction
There's an adage that holds that the best design is a stolen design. On that
basis, I recommend reading about how the Hurd console system works.
http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/hurd-daemons.html#console
http://gnu.org./software/hurd/hurd/console.html
The Hurd peopl
The way that you're going right now, you're going to surprise a lot of
people, possibly not pleasantly, in a little while. You've presented this as
a replacement of agetty and login. But the use cases of getty+login and what
you're doing are somewhat different. People expecting to get a
systemd-
I'll patch the comment. The code is up to you. (-:
--- consoled-pty-old.c 2013-12-05 12:53:24.0 +
+++ consoled-pty.c 2013-12-05 12:53:11.0 +
@@ -40,26 +40,45 @@
#include "sd-event.h"
/*
- * PTY
- * A PTY object represents a single PTY connection between a master and a
In your terminal_run_child() function you invoke the (login) shell for the
terminal as, effectively, "$SHELL" "-il". Don't do that. Distributions such
as Debian have spent a fair while getting rid of bashisms from the init system
and here you are putting more of them in. (-:
https://wiki.debi
29 matches
Mail list logo