[SOLVED] Samba Won't Stop Autostarting [ACTUALLY IT DOES!]

[josch]

-------------------------------------------------------- edit --------------------------------------------------------
Actually it does work as it should! I had just misunderstood the samba service. (see post #2)
---------------------------------------------------------------------------------------------------------------------

Hey,

as the title says, samba won't stop autostarting, although I disabled it in xbian-config.
Also xbian-config tells me that there is no samba service running.

But:

Terminal

xbian@xbian ~ $ sudo service samba status
[sudo] password for xbian:
[ ok ] nmbd is running.

In /usr/local/include/xbian-config/config/services it's:

Code:

samba:%%inetd

(But there is no entry for samba in /etc/inetd.conf. Should it be?)

But even if I change to

Code:

samba:nmbd

there is no change. Samba will still start on startup and xbian-config shows it as deactivated.


Anyone knows why?

How is the "service center" of xbian-config doing it's job?


PS: samba is linked in rc[2-6].d

[mk01]

(19th Jan, 2014 07:52 PM)josch Wrote:  1. as the title says, samba won't stop autostarting, although I disabled it in xbian-config.
Also xbian-config tells me that there is no samba service running.

2. In /usr/local/include/xbian-config/config/services it's:

Code:

samba:%%inetd

(But there is no entry for samba in /etc/inetd.conf. Should it be?)

But even if I change to

Code:

samba:nmbd

3. there is no change. Samba will still start on startup and xbian-config shows it as deactivated.

Anyone knows why?

1. smb is samba protocol support, nmb is only handling browsing name registrations and answer windows name queries on network. yes, until nmb is running, device with it will be listed on the network - but without smbd (samba service), there will be no support for windows sharing. machine will not show any shares, any services. because for this samba is needed, not nmbd.

if you check /etc/default/samba you will see, that samba is configured as "inetd". if you check init.d script you will see, that if this is inetd, smbd is not started. only nmbd is started as putting nmbd into inetd would make it pointless a bit. service manager is controlling smbd - so actual sharing service.

service manager is currently consolidating services from upstart, sysv and even inetd. but there is in debian still one quite frustrating tool - insserv. the problem is that until you specifically remove runlevel definitions from init.d startup script for any process, if any install helper tool in deb packages calls it without be specific, it will reinstall defaults back. so you remove link from rc?.d, then someone calls "insserv" and services will be back again.

but as I'm thinking about it now, XBian is providing already upstart samba scripts, although are not by default active. so you can do "rm /etc/init.d/samba" if you are scared seeing RPI on your network by name (although unaccessible)

2. http://forum.xbian.org/thread-1861-post-20099.html#pid20099

so shouldn't be empty, smbd should be there, but disabled (in case you disable service)

3. some level of disagreement or confusion will be there for all "multi daemon" services. there is one record (samba) actually having two components. this is a question of approach, whether service, having some components failed (not running) is running? I think not - it should indicate problem.

you are looking at it from other side - is service fully stopped if at least one component is running ? isn't. anytime you can split samba into two services - nmb and smb and it will be 100% acurate.

[josch]

Thanks for the enlightenment!

So everything is fine.