I have Samba starting at boot. But for some reason it doesn’t actually work, so I have to restart it manually after each system reboot. The screen-shot below demonstrates the situation: SWAT indicates that “smbd” is not running (and it doesn’t work indeed) while there is a “smbd” process (even two of them) on the system activity list and “smb” enabled in System Services. How to fix this issue? http://image.bayimg.com/dadjkaaee.jpg
I could not see your picture, so I did an edit, found the source and modified your post so we could see it. I hope that was OK with you?
As for smb, it might not want to run depending on your global section in your smb.conf file. You could get a copy with:
sudo cat /etc/samba/smb.conf
And post the results here in a message using the advance message editor and placing the text into a Code # field. I also have a bash script that can be used in editing such files you can find here:
SYSEdit - System File Editor - Version 1.00 - Blogs - openSUSE Forums
And for anyone who does not know how to use or get Samba going with SWAT, have a look here:
Samba S.W.A.T. - Samba Web Administration Tool Setup for openSUSE - Blogs - openSUSE Forums
AND
SWAT - Samba Web Administration Tool - Setup & Creation Script - 1.04 - Blogs - openSUSE Forums
Thank You,
I could not see your picture, so I did an edit, found the source and modified your post so we could see it. I hope that was OK with you?
Now I can’t see it… But if my descriotion is sufficient for the issue understanding - I don’t mind.
Here is the smb.conf:
# Samba config file created using SWAT
# from UNKNOWN (127.0.0.1)
# Date: 2012/08/09 02:38:00
[global]
map to guest = Bad User
passdb backend = smbpasswd
printcap name = cups
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path = \\%L\profiles\.msprofile
logon drive = P:
logon home = \\%L\%U\.9xprofile
domain master = No
usershare allow guests = Yes
usershare max shares = 100
idmap config * : backend = tdb
hosts allow = 192.168.0.190/192.168.0.200
cups options = raw
[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = No
[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
print ok = Yes
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
[Trash_Storage]
path = /windows/D/
admin users = Me
force group = users
read only = No
guest ok = Yes
[Geo]
path = /windows/E/
admin users = Me
force group = users
read only = No
guest ok = Yes
Have you really used the Linux username “Me” as suggested by “admin users = Me”?
Anyway, that’s not causing the issue, and it probably won’t break samba to have it there.
This is a clue: 3.6.3-34 suggests an early version of Samba. Whach version of openSUSE are you using?
Have you really used the Linux username “Me” as suggested by “admin users = Me”?
Actually I changed the username for the post (it’s just a paranoia)
My openSUSE version is 12.1 and I do not observe any samba updates available.
On 09/30/2012 05:56 AM, riabovvv wrote:
>
>> Have you really used the Linux username “Me” as suggested by “admin
>> users = Me”?
> Actually I changed the username for the post (it’s just a paranoia)
>
> My openSUSE version is 12.1 and I do not observe any samba updates
> available.
>
>
In 12.2 there is a broken RPM that creates a bug in Samba. It’s
discussed in a sticky at the top of the Network/Internet Forum. It might
apply here (or it might not). Have a look at it, see if you need to swap
out the software systemd-sysvinit and replace it with the software
sysvinit-init.
–
Regards
swerdna
see if you need to swap
out the software systemd-sysvinit and replace it with the software
sysvinit-init.
Thank you! It helped!
On 09/30/2012 08:46 AM, riabovvv wrote:
>
>> see if you need to swap
>> out the software systemd-sysvinit and replace it with the software
>> sysvinit-init.
> Thank you! It helped!
>
>
Do you mean that it’s completely fixed?
If that’s a “No”, then what problems remain?
–
Regards
swerdna
Now samba starts at boot and running so the issue is solved.