Subj : starting mis on system bootup
To   : All
From : Edmund Wong
Date : Fri Sep 16 2022 12:50 pm

Hi,

I currently run Mystic A47 on a Slackware system; but due
to infrastructure shuffling, I need to migrate it off to
something that is more up 24/7.

I've set up a new system that's based on CentOS 7.9
and I'm not familiar with systemd and how it
starts services.

What I currently have is this for my /etc/systemd/mis.service


[Unit]
 Description=Mystic BBS start

[Service]
 User=bbs
 ExecStart=/mystic/mis daemon
 ExecStop=/mystic/mis shutdown

[Install]
 WantedBy=default.target


But when I do the following:

1) systemctl daemon-reload
2) systemctl enable mis.service

3) systemctl start mis

I noticed in "journalctl -xe", I get that it first starts the
service then it shuts it down.

So I figured that maybe ExecStop shouldn't be in it, so I
removed it.  Did step 1 again.  then started mis.

When I do a  "ps -ax", I don't see it running.  When I try
to ssh into it using the ssh port,  it doesn't connect
as it's not listening, which is confirmed when I do a
"netstat -na".

Can someone point out what I'm missing?

Thanks

Ed

... Don't diet, download a virus to remove the FAT.

--- Mystic BBS v1.12 A47 2021/12/01 (Linux/32)
* Origin: Eagle's BBS (1:153/7083)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.