You can manually run
and it tells what it would do - without doing anything.
I tried that. Concerning the auth.log it says:
But that was yesterday when I set off the logrotate command manually.
The problem appears to be the test for -d /run/systemd/system. If the directory exists the script exits right away. (See my original post.)
I don't understand how it could detect the system timer by checking for the existence of that directory.
--- Post updated at 10:57 PM ---
Quote:
Originally Posted by Ralph
What if I restart the machine? Being in the /run directory won't it be recreated as 'system' when the system comes up again?
Quote:
Originally Posted by RudiC
"for a test" doesn't necessarily include a reboot...
The machine doesn't run 24/7. So unless I perform a test right after renaming the directory (which one?) it will be recreated as 'system' after a reboot. (I just rebooted and checked.)
Hey Guys,
i am new into shell programming and i have to do one script which have to record all the commands entered by a specific user.
Example of that, i have a system running on unix, several users are using this system, i have to create like a databse which will record every user entered that... (5 Replies)
Hy, I have a question
I have a directory in a unix server,
Some of my files have a diffrent access time,
from the time i accessed them last,
I think some one has copied it,it's not an important file,but none the less,it is my file,It mistakenly had a 777 permission( yes ,I know it is a noob's... (1 Reply)
Hi,
I am trying to write a script which would go search and get the info from the logs based on yesterday timestamp and write yesterday logs in new file. The log file format is as follows:
""""""""""""""""""""""""""... (3 Replies)
Hi ,
I am running an application on my windows and it logs are generated at /var/logs and for this i have to go this location and then do tail -f , Is there any command you can advise me so that when I execute this command at this location that logs get displayed fully and as the application... (3 Replies)
Hello all,
I am working on a perl script which will read weblogic logfile and send the error messages to Zenoss Monitoring tool. At present the script works and it can able to send the error messages to Zenoss. The problem comes when the logrotate has been applied to the weblogic log file. At... (3 Replies)
Appreciate help for the below issue.
Im using below code.....I dont want to attach the logs when I ran the perl twice...I just want to take backup with today date and generate new logs...What I need to do for the below scirpt..............
1)if logs exist it should move the logs with extention... (1 Reply)
Discussion started by: Sanjeev G
1 Replies
LEARN ABOUT MINIX
dh_systemd_enable
DH_SYSTEMD_ENABLE(1) Debhelper DH_SYSTEMD_ENABLE(1)NAME
dh_systemd_enable - enable/disable systemd unit files
SYNOPSIS
dh_systemd_enable [debhelperoptions] [--no-enable] [--name=name] [unitfile...]
DESCRIPTION
dh_systemd_enable is a debhelper program that is responsible for enabling and disabling 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.
In the complex case, you can call dh_systemd_enable and dh_systemd_start manually (by overwriting the debian/rules targets) and specify
flags per unit file. An example is colord, which ships colord.service, a dbus-activated service without an [Install] section. This service
file cannot be enabled or disabled (a state called "static" by systemd) because it has no [Install] section. Therefore, running
dh_systemd_enable does not make sense.
For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_systemd_enable quota.service and
dh_systemd_enable --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. That is controlled by dh_systemd_start(1) (using e.g. its
--no-start option).
--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_systemd_enable looks for and installs files named debian/package.name.service instead of the usual debian/package.service.
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.
Note that dh_systemd_enable should be run before dh_installinit. The default sequence in dh does the right thing, this note is only
relevant when you are calling dh_systemd_enable manually.
SEE ALSO dh_systemd_start(1), debhelper(7)AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_ENABLE(1)