Hi everybody,
I’m new to OpenSUSE, but I’ve used several Linux distributions before. And usualy when I install “cups” package, an initscript called /etc/init.d/cups is installed. But after installing “cups” package in OpenSUSE Leap 42.1 there is no /etc/init.d/cups.
Instead of using “/etc/init.d/cups start”, I’ve tried running “service cups start” but also failed.
Why there is no “/etc/init.d/cups” script?
How may I start the cups daemon?
Thanks
Ok. I’ve discovered the problem.
There is a “/usr/lib/systemd/system/cups.service” file, that means that “service cups start” should work. But it fails because I’m running it in a “chrooted” environment.
Thank you very much!
You’re using init5 commands which is being deprecated across the vast majority of distros (at different rates).
Recommend you learn the systemd commands.
In this case, the help command will list your options for the command systemctl to search for apps/services, to stop, start, restart, enable (run as a service), etc. You’ll likely have to run them from within your chroot to be effective within the chroot.
systemctl --help
Depending on your objectives for running a chroot, you may want to take a look at systemd-nspawn which will set up the equivalent of a chroot automatically applying many security configurations you normally have to set up manually for a chroot. You may also want to take a look at LXC or Docker containers which are both supported in openSUSE.
TSU
On 02/05/2016 10:26 AM, tsu2 wrote:
>
> system25;2752545 Wrote:
>> Ok. I’ve discovered the problem.
>>
>> There is a “/usr/lib/systemd/system/cups.service” file, that means that
>> “service cups start” should work. But it fails because I’m running it in
>> a “chrooted” environment.
>>
>> Thank you very much!
>
> You’re using init5 commands which is being deprecated across the vast
> majority of distros (at different rates).
>
> Recommend you learn the systemd commands.
>
> In this case, the help command will list your options for the command
> systemctl to search for apps/services, to stop, start, restart, enable
> (run as a service), etc. You’ll likely have to run them from within your
> chroot to be effective within the chroot.
>
> Code:
> --------------------
> systemctl --help
> --------------------
>
>
> Depending on your objectives for running a chroot, you may want to take
> a look at systemd-nspawn which will set up the equivalent of a chroot
> automatically applying many security configurations you normally have to
> set up manually for a chroot. You may also want to take a look at LXC or
> Docker containers which are both supported in openSUSE.
>
> TSU
>
>
systemd also supports tab expansion which will make it easier to use. use
code
systemd start <tab><tab>
/code
for a list of services that can be started. The same goes for stopping a
service.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
On 02/05/2016 10:26 AM, tsu2 wrote:
>
> system25;2752545 Wrote:
>> Ok. I’ve discovered the problem.
>>
>> There is a “/usr/lib/systemd/system/cups.service” file, that means that
>> “service cups start” should work. But it fails because I’m running it in
>> a “chrooted” environment.
>>
>> Thank you very much!
>
> You’re using init5 commands which is being deprecated across the vast
> majority of distros (at different rates).
>
> Recommend you learn the systemd commands.
>
> In this case, the help command will list your options for the command
> systemctl to search for apps/services, to stop, start, restart, enable
> (run as a service), etc. You’ll likely have to run them from within your
> chroot to be effective within the chroot.
>
> Code:
> --------------------
> systemctl --help
> --------------------
>
>
> Depending on your objectives for running a chroot, you may want to take
> a look at systemd-nspawn which will set up the equivalent of a chroot
> automatically applying many security configurations you normally have to
> set up manually for a chroot. You may also want to take a look at LXC or
> Docker containers which are both supported in openSUSE.
>
> TSU
>
>
systemd also supports tab expansion which will make it easier to use. use
code
systemd start <tab><tab>
/code
for a list of services that can be started. The same goes for stopping a
service.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996