On 04/16/14 09:38, Claude Jones wrote:
On 04/15/2014 05:16 PM, Joe Zeff wrote:
>
> There isn't such a thing (AFAIK) as service.service. Try this, as root:
>
> systemctl start cups.service
>
> And see if it starts up properly.
well, there is no output at all when I run that, but if I check the status after running
it, I get the same as I posted earlier:
[root@localhost ~]# systemctl start cups.service
[root@localhost ~]# systemctl status cups service
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: inactive (dead) since Tue 2014-04-15 21:14:53 EDT; 33s ago
Process: 3663 ExecStart=/usr/sbin/cupsd -f (code=killed, signal=TERM)
Main PID: 3663 (code=killed, signal=TERM)
Apr 15 21:14:53 localhost.localdomain systemd[1]: Started CUPS Printing Service.
service.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
BUT: I see an error in that status command - it should say cups.service so I try again:
[root@localhost ~]# systemctl status cups.service
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: inactive (dead) since Tue 2014-04-15 21:14:53 EDT; 4min 7s ago
Process: 3663 ExecStart=/usr/sbin/cupsd -f (code=killed, signal=TERM)
Main PID: 3663 (code=killed, signal=TERM)
Does it die if you try to start cupsd manually from the command line?
[root@meimei ]# /usr/sbin/cupsd -f
for example....
--
Getting tired of non-Fedora discussions and self-serving posts