We created a service unit that fires off a script to send an email when the file changes. In this example we set up a systemd path unit to monitor the /etc/passwd file for changes. For more information on using journalctl read " Viewing logs with journaltcl".
You can also use journalctl to check on your. Jan 25 13:30:00 putor systemd: passwd-mon.path: Succeeded. Jan 25 13:10:57 putor systemd: Started "Monitor the /etc/passwd file for changes". To check the logs generated by your path unit, use journalctl with the -u option. In addition their logs are available in the systemd journal via journalctl. This means you can control them with systemctl. One of the advantages of using systemd path (or timer) units is that they operate like normal services. Checking Your Path Unit Logs with Journalctl Looks like everything went off without a hitch. Mail -S sendwait -s "ETC PASSWD CHANGED ON $(hostname)" Create a file called email-alert.sh in the /usr/local/bin/ directory with the following contents. Let's start by creating a simple script that will send an email alert to our administrators. Path unit to monitor the file or directory.Service unit to launch the script when an event is observed.In order to create a functional path unit we need three files. In this example we will create a path unit to send an email alert if the /etc/passwd file changes on our system. Once the event triggers, systemd can execute a script via a service unit. Systemd path units allow you to monitor files and directories (paths) for an event. In today's article we are examining another unit file called path units. In a past article we discussed using systemd timer units to schedule jobs and their pros and cons over crond.
0 kommentar(er)
