Hi. I go to yast and start the smb service. It starts OK and works as expected. But when i restart my computer, I have to go back to yast and start it again. I’m on 12.3 KDE. On prior version of Suse I came to expect that runlevel services started in yast should “stick” No?
Have a look at my blog post on Samba and the bash script I have posted there. Read all the way to the end for added info on setting up Samba. You should find a solution to your problems.
S.A.C.T. - Samba Automated Configuration Tool - Version 1.03 - Blogs - openSUSE Forums
Thank You,
On 2013-04-03 04:26, JJMT wrote:
> Hi. I go to yast and start the smb service.
Yast implementation of this in 12.3 is faulty. You have to activate the
services yourself, manually.
su -
chkconfig nmb
chkconfig nmb on
chkconfig smb
chkconfig smb on
This should work as far as telling the system to start those services at
boot. They may fail for a different reason, like network not running at
that instant.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 04/02/2013 10:26 PM, JJMT pecked at the keyboard and wrote:
> Hi. I go to yast and start the smb service. It starts OK and works as
> expected. But when i restart my computer, I have to go back to yast and
> start it again. I’m on 12.3 KDE. On prior version of Suse I came to
> expect that runlevel services started in yast should “stick” No?
You have to remember that there are no runlevels in 12.3 which relies on
systemd to start all services. You need to enable the service and also
start the service or reboot. 
This worked. I’ve been managing services with yast for years. Kinda disappointing yast didn’t do this for me. Still, problem solved. Thanks!
On 2013-04-03 14:26, JJMT wrote:
> This worked. I’ve been managing services with yast for years. Kinda
> disappointing yast didn’t do this for me. Still, problem solved. Thanks!
Yes, it is disappointing
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)