OK!
So :
- systemctl is the (dynamic) evolution of traditional way to mange the services.
- they are services (even if they are very common and important) that have to be installed...
Thank you for your answers..
Regards
On Tue, Mar 31, 2015 at 9:51 PM, Rick Stevens <ricks@xxxxxxxxxxxxxx> wrote:
On 03/31/2015 09:05 AM, Angelo Moreschini wrote:
Hi,
I am learning Linux and, just in order to do exercises, I wanted to
monitor the functioning of services that, I thing, should run on fedora.
So, with the command : service *smartd* status
I got :
Redirecting to /bin/systemctl status *smartd.service*
● smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon
Loaded: loaded (/usr/lib/systemd/system/smartd.service; enabled)
Active: active (running) since Tue 2015-03-31 07:48:18 IDT; 10h ago
Main PID: 701 (smartd)
CGroup: /system.slice/smartd.service
└─701 /usr/sbin/smartd -n -q never
the same for *cups*....
● cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: active (running) since Tue 2015-03-31 07:48:51 IDT; 10h ago
.............................
..............................
but I was wonder that services as :
*DHCP, SAMBA*, ..... was not working.... :
the command : sudo service *samba* status
give me :
Redirecting to /bin/systemctl status samba.service
● samba.service
Loaded: not-found (Reason:*No such file or directory*)
Active: inactive (dead)
for *SAMBA* I give a look to check if it is installed, and I found:
sudo yum list installed | grep samba
samba-client.x86_64 2:4.1.17-1.fc21 @updates
samba-common.x86_64 2:4.1.17-1.fc21 @updates
samba-libs.x86_64 2:4.1.17-1.fc21 @updates
samba-winbind.x86_64 2:4.1.17-1.fc21 @updates
samba-winbind-clients.x86_64 2:4.1.17-1.fc21 @updates
samba-winbind-modules.x86_64 2:4.1.17-1.fc21 @updates
So, ...
after this test I am confuse .......
What is the reason why some important services are not running by
default on Fedora 21?
Could I have an explanation ?
First, the "service" command is the old interface to the initscripts
mechanism which (unfortunately IMHO) is being replaced by systemd and
systemctl. For convenience, things like "service samba start" is being
redirected to "systemctl start samba.service". This will not continue
for much longer (it is deprecated).
You don't have the Samba server installed, so systemctl is telling you
there is no "samba.service" thing defined. If you DID have the Samba
server installed, the systemctl target would be "smb.service".
You don't need to run the Samba server if all you're going to do is try
to mount CIFS shares from a Windows server. All that requires is the
client code (which you do have installed).
The same is true of DHCP. You most likely don't have a DHCP server installed or configured, so "systemctl start dhcpd.service" isn't going
to buy you anything either.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- To err is human, to moo bovine. -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
