Hello
I created a startup script in rhel7 however the sym links are not in the run level ( /etc/rc3.d/ /etc/rc4.d/ etc)

I see its enabled :
systemctl list-unit-files | grep my1
my1.service enabled
Shows as enabled

Also how do I delete the my1 from the list, I know you can mask it but is there a del option? chkconfig --del my equivalent to systemctl ?

Thanks

this has nothing to do with systemd, it's the old init system (sysvinit iirc).

you MUST learn systemd!!!

Great !
But what the help here for my ask?

Like I said ; I see it as enabled however when I restart I dont see the service running/active state.
That is my main issue.

Lets take an example: test.service
# systemctl status test.service
● test.service - Test sample script
Loaded: loaded (/etc/systemd/system/test.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2017-10-18 11:46:35 EDT; 1h 9min ago
Process: 1339 ExecStart=/var/tmp/test_script.sh (code=exited, status=0/SUCCESS)
Main PID: 1339 (code=exited, status=0/SUCCESS)

The service file:
#cat /etc/systemd/system/test.service
[Unit]
Description=Test sample script
After=network.target

[Service]
Type=simple
ExecStart=/var/tmp/test_script.sh
TimeoutStartSec=0
user=root

[Install]
WantedBy=default.target

The script:
#cat /var/tmp/test_script.sh
#!/bin/bash
echo "This is a sample script to test auto run during boot" > /var/tmp/script.out
echo "The time the script run was --> `date`" >> /var/tmp/script.out

The perms:
# ls -l /var/tmp/test_script.sh
-rwx------. 1 root root 164 Oct 18 11:41 /var/tmp/test_script.sh

Enabled:
# systemctl is-enabled test.service
enabled
# ls -l /etc/systemd/system/default.target.wants/test.service
lrwxrwxrwx. 1 root root 32 Oct 18 13:04 /etc/systemd/system/default.target.wants/test.service -> /etc/systemd/system/test.service


# systemctl is-active test.service
inactive

Did your output file (/var/tmp/script.out) get created and contain the desired information?

Since the script is not a real daemon or service it isn't going to continuously run.

Hey Michaelk
Ok the output did get written to it at boot.

Ok so I another script with start,stop case statements
Updated the systemStatus.sh.service file
Ran the systemctl reenable systemStatus

However when I checked sysstat.service its in these 2 locations:

/sys/fs/cgroup/devices/system.slice/sysstat.service
/sys/fs/cgroup/systemd/system.slice/sysstat.service

When I check the service I created its not the locations as sysstat.service , sshd.service etc are in
# find / -name systemStatus.sh.service
/etc/systemd/system/default.target.wants/systemStatus.sh.service
/etc/systemd/system/systemStatus.sh.service

Also ran a reboot

I am not sure if its the placement of the service file or the file name itself the cause. (Will try it out)
Or the variables in the file

The startus service unit file
[Unit]
Description=systemStatus script
After=network.target

[Service]
ExecStart=/var/tmp/systemStatus.sh start
ExecStop=/var/tmp/systemStatus.sh stop

[Install]
WantedBy=default.target

I got it work in lab! yay!

Added to the following service file
RemainAfterExit=yes

Ran systemctl daemon-reload "service file" << no quotes ; at this point you can systemctl restart service; systemctl reenable service
(Since it isnt prod I decided to reboot to see if the service is online after reboot -- viola! it did)

During trial period I had used: type=simple, type=oneshot, type=forking(sshd had this)
I also used user=root -- none of them mattered.