OS: openSUSE 13.1 (Bottle) (armv7hl) uname -a: Linux linux.site 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/Linux
So this is my first attempt at starting a service at boot with systemd. I've done this with inittab in the past,
but I'm having trouble getting mgetty to start during boot. If I check the status of mgetty.service I can see
that it failed, but there really isn't any useful debugging information there...
Here is the Status output: *Does the word "disabled" and/or "inactive (dead)" in the message below mean it didn't even try to start it?
There is also no information in mgetty's log (*/var/log/mgetty.ttyACM0) for that device (*nor is there anything about
mgetty in /var/log/messages with today's date). It almost seems like systemd didn't even attempt to start mgetty.
But, I CAN start mgetty from the command line manually with "systemctl start mgetty.service" and then if I
check the staus again I can see it started up successfully...
# systemctl status mgetty
mgetty.service - Smart Modem Getty(mgetty)
Loaded: loaded (/usr/lib/systemd/system/mgetty.service; disabled)
Active: active (running) since Wed 2014-09-24 11:01:41 EDT; 4s ago
Main PID: 1711 (mgetty)
└─1711 /usr/sbin/mgetty -D -s 57600 -n 2 -m "" AT+VCID=1 /dev/ttyACM0
Sep 24 11:01:41 linux.site systemd: Started Smart Modem Getty(mgetty).
Here is my "/usr/lib/systemd/system/mgetty.service"File:
Should I be seeing something in the /var/log/messages file if it did in fact attempt to start? And, since it starts successfully
when I start it manually with systemctl start it seems like maybe it's attempting to start too early, but I can't be sure
since there is no debugging/log information about it...
Any ideas what I can try here to get this started at boot?
Any thoughts or suggestions would be greatly appreciated...
Thanks in Advance,
---------- Post updated at 11:54 AM ---------- Previous update was at 11:16 AM ----------
Sorry, I think I figured it out....
After Googling around a bit more I found the option below for systemctl:
After entering the "systemctl enable mgetty.service" command (*which printed out a "ln -s" command to STDOUT, but I don't remember
exactly what it linked to...), and re-running "systemctl status mgetty" I can see it says enabled now, instead of disabled like it was previously.
So I then rebooted and after I logged in and opened up a terminal and checked the status, it showed it was running... See below: