mjhjmtu

I have a bash script that detects when new directories are created under /var/log/myhosts/. When a new directory is created, it should create a directory named "myfolder" under it.

/etc/myscript.sh

#!/bin/bash
/usr/bin/inotifywait -m /var/log/myhosts -e create -e moved_to |
 while read path action file; do
 /usr/bin/mkdir -p "/var/log/myhosts/$file/myfolder"
 done

I want to run this script from a systemd service unit on boot. I created and enabled the following systemd service unit:

/etc/systemd/system/myhosts.service

[Unit]
Description=Watches /var/log/myhosts/ for new directories
After=rsyslog.service

[Service]
Type=simple
ExecStart=/etc/myscript.sh

[Install]
WantedBy=multi-user.target

This script works as expected if I run it like:

bash /etc/myscript.sh
sh /etc/myscript.sh
cd /etc/ -> ./myscript.sh
systemctl start myhosts.service
crontab -e -> @reboot /etc/myscript.sh -> works after reboot

If I enable the systemd service unit and reboot my Linux system, after the reboot systemctl status myhosts.service says that the service is running, ps -ef | grep my returns that there is a process for the script and the script is running properly, but when I create directories in /var/log/myhosts/ it doesn't create a directory myfolder inside them.

I just want to know why the systemd service unit approach doesn't work after reboot. What am I doing wrong? As mentioned above, the crontab @reboot /etc/myscript.sh approach works as expected.