SuSE 9.0 smbd -D && nmbd -D autostart

DaFrEQ · 04-14-2004, 02:47 PM

Hey all.

I'm having troubles getting the smbd -d and nmbd -d to start during bootup.

I tried using YaST2 Runlevel Editor, but there isn't anything located in the /etc/init.d dir partaining to the smbd or nmbd.

I also wrote a simple script and put it in the init.d dir and the runlevel editor saw it. I set it up to load automatically under inits 2, 3, & 4.
It loads the smbd -D but not the nmbd -D.
Then I have to manually execute: #nmbd -D
But then the printer isn't accesible to other machines.

When I removed the nmbd -D script from auto loading, it still failed to leave access to the printer to other machines.
I had to remove the smbd -D and nmbd -D scripts from autoloading and reverted back to manual execution of the two commands.
It works fine when I execute it manually, but I need it to load automatically.

Any ideas?

Tnx.
L8rz

beyond_2000 · 04-17-2004, 01:08 PM

why not try this command: chkconfig
because i had uninstalled my suse9, you can use
chkconfig --list smbd to find it out, if you got it, just type chkconfig --add smbd
then it will start at run level 3,5.
good luck.

DaFrEQ · 04-19-2004, 12:26 PM

Thing is,

smbd and nmbd are not current services. I'm not using the built in Samba server in SuSE.
I installed the latest from source because SuSE's version was causing problems with my printer.

So, again, I need a way to start these two services automatically that will eliminate the errors of before.

As the previous thread stated:
Every time I setup the smbd -D & nmbd -D to start automatically, it doesn't work properly. Only when I run the commands manually does the samba server work properly.

DaFrEQ · 04-20-2004, 05:16 PM

objorkum · 04-23-2004, 06:28 PM

If Samba is installed trough YaST it's very easy:

Code:

cd /etc/init.d
insserv smb
insserv nmb

You have now activated the SMB and the NMB daemon during startup. You can also take a look at those scripts, but they are fine. insserv is the same as runlevel editor. insserv -r <script> removes a script from the runlevels (rcX.d)

A reason why your script didn't work, might be that you didn't requite $network and $named. Runlevel 3 and 5 is enough when making own scripts usually.

beyond_2000 · 04-24-2004, 04:10 AM

Come on , objorkum ,i never got this command.
does it really works ?