I've had a few problems with systemd and a very simple start/stop script too. I was asked to set something that that was not a true service to run at boot time. After much testing and tracing, the problem I had was that systemd would run the start and then run the stop. Weird, but that's what it seemed to do. I got past this by adding a RemainAfterExit=yes clause in my service definition file.
The whole thing in /etc/systemd/system/robin.service (okay I changed the name) is pasted below:
After that it is a start/stop script much like to have that is being called.
I was testing Fedora 16 mostly to check the new features. One thing that caught my eye as a systems admin is the systemd which is incorporated in Fedora for quite a while now.
From the first look of it, this appears more close to Solaris's SMF. With parallelization capabilities, advanced... (0 Replies)
I am writing a program that must determine certain things about services. How can I, or my program, determine which services are started automatically when a given target becomes active. It is my impression that just looking in the target's .wants directory is inadequate because of other... (2 Replies)
I'm on Arch and I have a strange issue with systemctl hibernate command. It hibernates and resumes just fine (I have TuxOnIce), but in the last stage of resume, it completely shuts down my laptop screen, so I cannot see anything even though I know the system resumed just fined and the desktop is... (1 Reply)
Hallo
I don't know where to put my question so I put it here.
I want that systemd let run a script but only on shutdown or reboot
and before the system umount the mounted devices.
I look on google but only a little information is found and not working
Until no, I don't find an solution for... (1 Reply)
Hello All,
OS: openSUSE 13.1 (Bottle) (armv7hl)
uname -a: Linux linux.site 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/Linux
So this is my first attempt at starting a service at boot with systemd. I've done this with inittab in the past,
but I'm having... (0 Replies)
Hi All,
I had a startup script (rc3.d/S01getinput) which will accept user inputs during the boot up in console. Basically it will prompt for input. It was working fine in RHEL6.
Now I have migrated to RHEL 7 and script gets executed as part of the boot up process. But it does not... (1 Reply)
hi moring everyone,
i has used systemd-timer running the task, i set every 5 second execute 1 times,but the systemd-timer don't by that also random times execute.
what's reason.
testest.timer configure
------------------------------------------------------------------------
... (2 Replies)
Hey there.
I'm new in write bash scripts in fact this is my first one so please be patient ;). Also english is not my native language but i hope you understand me anyway.
I installed xubuntu on my mothers laptop and every time a new version update gets installed the keyboard doesn't work... (9 Replies)
journalctl --since "tomorrow"
By idea to show magazines from tomorrow. As it is illogical.
Tell me what is the essence of the team with the key tomorrow?
Code tags please (1 Reply)
Discussion started by: alekseev
1 Replies
LEARN ABOUT NETBSD
dh_installsystemd
DH_INSTALLSYSTEMD(1) Debhelper DH_INSTALLSYSTEMD(1)NAME
dh_installsystemd - install systemd unit files
SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files.
In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the
machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from
sysvinit to systemd and back.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and
dh_installsystemd --name=quotarpc quotarpc.service.
FILES
debian/package.service, debian/package@.service
If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build
directory.
debian/package.tmpfile
If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is
currently only used by systemd.)
debian/package.target, debian/package@.target
If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build
directory.
debian/package.socket, debian/package@.socket
If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build
directory.
debian/package.mount
If this exists, it is installed into lib/systemd/system/package.mount in the package build directory.
debian/package.path, debian/package@.path
If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build
directory.
debian/package.timer, debian/package@.timer
If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build
directory.
OPTIONS --no-enable
Disable the service(s) on purge, but do not enable them on install.
Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should
not be started.
--name=name
Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used,
dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
Moreover, maintainer scripts are only generated for units that match the given name.
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should
not be enabled.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
SEE ALSO debhelper(7)AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)