Everyone:
I have two computers, one desktop and one laptop. I did clean installs on both. In the process, I retired a third computer that had been running samba without incident for years.
Today I can get samba running on both machines. But: I have to execute two commands:
$ sudo /sbin/smbd -D $ sudo /sbin/nmbd -D
by hand, in a terminal (Konsole), every time I start or restart either computer.
The system-config-services app fails to note that smbd or nmbd are even available for starting.
How do I get those two daemons to start automatically, so that I don't have to type those two commands every time? Because until I do, I have no file-sharing capability. (I have yet another computer on my network: a dedicated Windows box that I use for video capturing. I've said on other threads I am not satisfied with the video-capture and DVD authoring support Linux provides, and note that Linux does not support Blu-ray, in playback or especially in burning. So samba is a must for me.)
Temlakos
On 06/18/14 20:29, Temlakos wrote:
I have two computers, one desktop and one laptop. I did clean installs on both. In the process, I retired a third computer that had been running samba without incident for years.
Today I can get samba running on both machines. But: I have to execute two commands:
$ sudo /sbin/smbd -D $ sudo /sbin/nmbd -D
by hand, in a terminal (Konsole), every time I start or restart either computer.
The system-config-services app fails to note that smbd or nmbd are even available for starting.
How do I get those two daemons to start automatically, so that I don't have to type those two commands every time? Because until I do, I have no file-sharing capability. (I have yet another computer on my network: a dedicated Windows box that I use for video capturing. I've said on other threads I am not satisfied with the video-capture and DVD authoring support Linux provides, and note that Linux does not support Blu-ray, in playback or especially in burning. So samba is a must for me.)
And the output of....
systemctl status smb.service
and
systemctl status nmb.service
is?
https://fedoraproject.org/wiki/Systemd
On 06/18/2014 08:40 AM, Ed Greshko wrote:
On 06/18/14 20:29, Temlakos wrote:
I have two computers, one desktop and one laptop. I did clean installs on both. In the process, I retired a third computer that had been running samba without incident for years.
Today I can get samba running on both machines. But: I have to execute two commands:
$ sudo /sbin/smbd -D $ sudo /sbin/nmbd -D
by hand, in a terminal (Konsole), every time I start or restart either computer.
The system-config-services app fails to note that smbd or nmbd are even available for starting.
How do I get those two daemons to start automatically, so that I don't have to type those two commands every time? Because until I do, I have no file-sharing capability. (I have yet another computer on my network: a dedicated Windows box that I use for video capturing. I've said on other threads I am not satisfied with the video-capture and DVD authoring support Linux provides, and note that Linux does not support Blu-ray, in playback or especially in burning. So samba is a must for me.)
And the output of....
systemctl status smb.service
and
systemctl status nmb.service
is?
$ systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: inactive (dead)
[Temlakos@temlakos ~]$ systemctl status nmb.service nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled) Active: inactive (dead)
Temlakos
On 06/18/14 20:59, Temlakos wrote:
$ systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: inactive (dead)
[Temlakos@temlakos ~]$ systemctl status nmb.service nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled) Active: inactive (dead)
Yep.... disabled
systemctl enable smb.service systemctl enable nmb.service
And they will start at boot time....
systemctl start smb.service systemctl start nmb.service
To get them going without having to boot.
systemd is the "new" kid in town. Read up on it in the link I provided.
On 06/18/2014 09:02 AM, Ed Greshko wrote:
On 06/18/14 20:59, Temlakos wrote:
$ systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: inactive (dead)
[Temlakos@temlakos ~]$ systemctl status nmb.service nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled) Active: inactive (dead)
Yep.... disabled
systemctl enable smb.service systemctl enable nmb.service
And they will start at boot time....
systemctl start smb.service systemctl start nmb.service
To get them going without having to boot.
systemd is the "new" kid in town. Read up on it in the link I provided.
Thank you for that tip.
Bottom line: both those services are now enabled, and activate cleanly on system restart (or start from shutdown).
Now when I try to start either one in runtime, I get an SELinux alert. But as long as I simply do a restart or a cold start, such alerts do not happen. (I always "sudo" such commands, BTW. I made myself a member of Wheel.)
Connectivity is automatic once again.
Temlakos
On Wed, Jun 18, 2014 at 09:20:45 -0400, Temlakos temlakos@gmail.com wrote:
Now when I try to start either one in runtime, I get an SELinux alert. But as long as I simply do a restart or a cold start, such alerts do not happen. (I always "sudo" such commands, BTW. I made myself a member of Wheel.)
Are you using systemctl to start them? If you just run the binaries the proper process labelling (and other things) might not be setup.
On Wednesday, June 18, 2014 09:02:27 PM Ed Greshko wrote: On 06/18/14 20:59, Temlakos wrote:
$ systemctl status smb.service smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: inactive (dead)
[Temlakos@temlakos ~]$ systemctl status nmb.service nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled) Active: inactive (dead)
Yep.... disabled
systemctl enable smb.service systemctl enable nmb.service
And they will start at boot time....
systemctl start smb.service systemctl start nmb.service
To get them going without having to boot.
systemd is the "new" kid in town. Read up on it in the link I provided.
It gets a little funky on Fedora because some services are started automatically like Bumblebeed and some aren't like Thinkfan unline Arch were everything is up to user.
Sudhir.
Hi
On Wed, Jun 18, 2014 at 1:15 PM, Sudhir Khanger wrote:
It gets a little funky on Fedora because some services are started automatically like Bumblebeed and some aren't like Thinkfan unline Arch were everything is up to user.
http://fedoraproject.org/wiki/Starting_services_by_default
Rahul
On 06/18/2014 05:29 AM, Temlakos wrote:
Today I can get samba running on both machines. But: I have to execute two commands:
$ sudo /sbin/smbd -D $ sudo /sbin/nmbd -D
by hand, in a terminal (Konsole), every time I start or restart either computer.
The system-config-services app fails to note that smbd or nmbd are even available for starting.
How do I get those two daemons to start automatically, so that I don't have to type those two commands every time? Because until I do, I have no file-sharing capability.
Put the two commands in a shell script, without sudo, and call them from /etc/rc.local.
-
Bruno Wolff III -
Ed Greshko -
Joe Zeff -
Rahul Sundaram -
Sudhir Khanger -
Temlakos