Re: [opensuse] nmbd does not start at boot in openSUSE 12.2
Anton, I haven't received your answer in my mailbox, so I am copy-pasting it from the web-site: -------------------------------------------------------------------------------------------------- Istvan Gabor said the following on 08/03/2013 06:12 PM: nmbd demon does not start when my openSUSE 12.2 system is booted. smbd demon starts normally. This is openSUSE 12.2 with up to date kernel and samba packages, using systemd init. # ps -e|grep -i smb 3082 ? 00:00:00 smbd 3230 ? 00:00:00 smbd lnx:~ # ps -e|grep -i nmb lnx:~ # How can I fix this? If you are using systemd then the daemons start via .service descriptions. Grep around to see what the one that starts smbd contains and see if there is one that isn't enables for nmbd and winbindd. Try starting the manually as described in https://bbs.archlinux.org/viewtopic.php?id=147305 If that works then enable them (as described in many other threads here), but do check dependencies (and required files, libraries, directories etc) and the order they should come up. ---------------------------------------------------------------------------------------- Unfortunately it did not help. 1. It took a long time until I found out that the service names in openSUSE are: smb.service and nmb.service, instead of smbd.service and nmbd.service as mentioned at the site you linked. 2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.) 3. These are the results of grep and systemctl status commands: # ps -e|grep -i smb 2893 ? 00:00:00 smbd 2946 ? 00:00:00 smbd # # # ps -e|grep -i nmb # # # systemctl status smb.service smb.service - LSB: Samba SMB/CIFS file and print server Loaded: loaded (/etc/init.d/smb) Active: active (running) since Mon, 05 Aug 2013 14:14:41 +0200; 3min 2s ago Process: 2856 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/smb.service ├ 2893 /usr/sbin/smbd -D -s /etc/samba/smb.conf └ 2946 /usr/sbin/smbd -D -s /etc/samba/smb.conf Aug 05 14:14:41 lnx smb[2856]: Starting Samba SMB daemon ..done # # # systemctl status nmb.service nmb.service - LSB: Samba NetBIOS naming service over IP Loaded: loaded (/etc/init.d/nmb) Active: failed (Result: exit-code) since Mon, 05 Aug 2013 14:14:41 +0200; 3min 7s ago Process: 2814 ExecStart=/etc/init.d/nmb start (code=exited, status=7/NOTRUNNING) CGroup: name=systemd:/system/nmb.service Aug 05 14:14:41 lnx nmb[2814]: Starting Samba NMB daemon ..failed # # 4. I can start smbd manually: # systemctl start nmb.service # # systemctl status nmb.service nmb.service - LSB: Samba NetBIOS naming service over IP Loaded: loaded (/etc/init.d/nmb) Active: active (running) since Mon, 05 Aug 2013 15:19:58 +0200; 18s ago Process: 4625 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nmb.service └ 4634 /usr/sbin/nmbd -D -s /etc/samba/smb.conf Aug 05 15:19:58 lnx nmb[4625]: Starting Samba NMB daemon - Warning: /var/run/samba/nmbd.pid exists. ..done # 5. This is a new openSUSE 12.2 installation without any hacking. All packages are installed by YaST and samba was set up and configured by YaST as well. Should not it work out of the box? Any further help, possibly specific, is appreciated. Thanks! Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor said the following on 08/05/2013 07:22 AM:
Anton,
I haven't received your answer in my mailbox, so I am copy-pasting it from the web-site:
That's curious ... [Big Snip]
If you are using systemd then the daemons start via .service descriptions. Grep around to see what the one that starts smbd contains and see if there is one that isn't enables for nmbd and winbindd. Try starting the manually as described in https://bbs.archlinux.org/viewtopic.php?id=147305
If that works then enable them (as described in many other threads here), but do check dependencies (and required files, libraries, directories etc) and the order they should come up.
----------------------------------------------------------------------------------------
Unfortunately it did not help.
1. It took a long time until I found out that the service names in openSUSE are: smb.service and nmb.service, instead of smbd.service and nmbd.service as mentioned at the site you linked.
I can't say that surprises me; I'll have to look to Fedora some time to see if Suse is at variance or if ArchLinux is at variance. Either way, its not really significant; its not as if there is a 'standard' here. Or maybe not https://bugzilla.redhat.com/show_bug.cgi?id=830589
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
It would be, depending on distribution and release, under /etc/systemd, lib/systemd or /usr/lib/systemd. Systemd uses a couple of other suffices as well. Its all documented in the man pages. The exception here is the 'autogenerated' units. For example, systemd scans the /etc/fstab file to generate units to take care of mounting. You can see the result with systemctl -a | grep mount Similarly unless there are other specific entries, systemd supports, in its backward compatibility mode, entries from /etc/init.d that haven't been converted. This is what you are seeing. I'm sure Cristian can explain better. And yes its documented.
3. These are the results of grep and systemctl status commands:
# ps -e|grep -i smb 2893 ? 00:00:00 smbd 2946 ? 00:00:00 smbd # # # ps -e|grep -i nmb # # # systemctl status smb.service smb.service - LSB: Samba SMB/CIFS file and print server Loaded: loaded (/etc/init.d/smb) Active: active (running) since Mon, 05 Aug 2013 14:14:41 +0200; 3min 2s ago Process: 2856 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/smb.service ├ 2893 /usr/sbin/smbd -D -s /etc/samba/smb.conf └ 2946 /usr/sbin/smbd -D -s /etc/samba/smb.conf
The 'loaded' line tells us a lot. There isn't a specific smb unit, its part of the automatic generation of entries (that remain to be converted) of /etc/init.d entries which I mentioned above. systemctl -a| grep smb However it does give you enough information to create a a custom smb.service unit of your own in /etc/systemd/ Its not difficult and its not scary. You have plenty of other examples to show you how its done.
Aug 05 14:14:41 lnx smb[2856]: Starting Samba SMB daemon ..done # # # systemctl status nmb.service nmb.service - LSB: Samba NetBIOS naming service over IP Loaded: loaded (/etc/init.d/nmb) Active: failed (Result: exit-code) since Mon, 05 Aug 2013 14:14:41 +0200; 3min 7s ago Process: 2814 ExecStart=/etc/init.d/nmb start (code=exited, status=7/NOTRUNNING) CGroup: name=systemd:/system/nmb.service
Same basic comments. In this case look to the log files to see why it did not start.
Aug 05 14:14:41 lnx nmb[2814]: Starting Samba NMB daemon ..failed # #
4. I can start smbd manually:
# systemctl start nmb.service # # systemctl status nmb.service nmb.service - LSB: Samba NetBIOS naming service over IP Loaded: loaded (/etc/init.d/nmb) Active: active (running) since Mon, 05 Aug 2013 15:19:58 +0200; 18s ago Process: 4625 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nmb.service └ 4634 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
So what is the difference between this and the above? Possibly a dependency. I've found that I've had to tweek dependencies on my systems. I've commented on this elsewhere on this forum. You may need something of the form After=syslog.target network.target nmb.service winbind.service but I'm not knowledgeable enough about Samba to be sure of the details as to which of nmbd and smbd should start first. But yes, they should most certainly be dependent on the network being up! And if you want to do any debugging you'll want syslog to be up!
Aug 05 15:19:58 lnx nmb[4625]: Starting Samba NMB daemon - Warning: /var/run/samba/nmbd.pid exists. ..done #
5. This is a new openSUSE 12.2 installation without any hacking.
We'll I've had to hack my system fair bit for a variety of reasons, mostly, as I say, dependencies, but also because the start-up of Postfix wasn't working the way I wanted. Let me repeat that .... THE WAY I WANTED The 'out of the box' experience tries to be a 'one size fits all' and we know that the reality of the world is that such is rarely the case. So if you haven't hacked your machines you're letting someone else decide how you should be using it and its not working THE WAY YOU WANT IT TO
All packages are installed by YaST and samba was set up and configured by YaST as well. Should not it work out of the box?
I'm sorry, what part of the above don't you understand. Of course it works "out of the box", the way someone else thinks it should. Almost everyone here, certainly those of us who contribute and most certainly those who contribute regularly are in the class of people who want it to work differently than 'out of the box'. Clearly you too want it to work THE WAY YOU WANT IT TO and not the way it works out of the box. This is OpenSuse, not SLED. Heck, even the Fred Sixpack Windows users that I encounter seem to hack their systems! OBTW: Yast is *NOT* "systemd-aware". Don't expect Yast to be able to set up things to work with systemd!
Any further help, possibly specific, is appreciated.
You have enough in the above to create smb.service and nmb.service in /etc/systemd. Do check the man pages for smbd and nmbd as well as the systemd ones :-) -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-08-05 08:26 (GMT-0400) Anton Aylward composed:
Istvan Gabor composed:
1. It took a long time until I found out that the service names in openSUSE are: smb.service and nmb.service, instead of smbd.service and nmbd.service as mentioned at the site you linked.
I can't say that surprises me; I'll have to look to Fedora some time to see if Suse is at variance or if ArchLinux is at variance. Either way, its not really significant; its not as if there is a 'standard' here.
Or maybe not https://bugzilla.redhat.com/show_bug.cgi?id=830589
I booted F19 to take a look and found: /usr/lib/systemd/system/nmb.service /usr/lib/systemd/system/smb.service -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/5/2013 5:26 AM, Anton Aylward wrote:
Similarly unless there are other specific entries, systemd supports, in its backward compatibility mode, entries from /etc/init.d that haven't been converted. This is what you are seeing. I'm sure Cristian can explain better. And yes its documented. ... There isn't a specific smb unit, its part of the automatic generation of entries (that remain to be converted) of /etc/init.d entries which I mentioned above.
systemctl -a| grep smb
However it does give you enough information to create a a custom smb.service unit of your own in /etc/systemd/
Its not difficult and its not scary. You have plenty of other examples to show you how its done.
So is this the plan for the foreseeable future, or merely a kludge for the present so as to not to have to totally rebuild OpenSuse and Yast? Is auto-generation a sustainable mechanize? Then, circling around to the original problem, that if smb or nmb failing to start, does it make more sense to set up one's own smb.service than to fix the problem in the auto generation engine? It would seem that if opensuse is going to continue to use auto generation that the wisest fix would be to fix that, rather than end-running the entire process. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen said the following on 08/05/2013 01:31 PM:
On 8/5/2013 5:26 AM, Anton Aylward wrote:
Similarly unless there are other specific entries, systemd supports, in its backward compatibility mode, entries from /etc/init.d that haven't been converted. This is what you are seeing. I'm sure Cristian can explain better. And yes its documented. ... There isn't a specific smb unit, its part of the automatic generation of entries (that remain to be converted) of /etc/init.d entries which I mentioned above.
systemctl -a| grep smb
However it does give you enough information to create a a custom smb.service unit of your own in /etc/systemd/
Its not difficult and its not scary. You have plenty of other examples to show you how its done.
So is this the plan for the foreseeable future, or merely a kludge for the present so as to not to have to totally rebuild OpenSuse and Yast?
Is auto-generation a sustainable mechanize?
Auto-generation of WHAT? There seem tome to be a number of such 'auto-generators'. There's certainly the one that builds the .mount items from the /etc/fstab and that works quite well. This thread is about the one that tries to make use of the old /etc/init.d scripts that systemd is trying to replace. So why not catch up with Fedora and others and actually do that replacement? The OP wanted a fix. We're not talking about rebuilding the distribution, we're talking about customizing his system.
Then, circling around to the original problem, that if smb or nmb failing to start, does it make more sense to set up one's own smb.service than to fix the problem in the auto generation engine?
The problem with the scripts is that dependencies and sequencing were haphazard. Under systemd they are explicit. What gets started - or not - and in what order is made very clear. As I've mentioned, I've highly customized my DNS and I've found that I've had to very explicitly make Postfix, spamassassin and NTP dependent on DNS completing, and sometimes all the DNS tables (thank you Peter Lowe http://pgl.yoyo.org/) take a while to load. So, which should come first, smbd or nmbd? Will they depend on winbindd?
It would seem that if opensuse is going to continue to use auto generation that the wisest fix would be to fix that, rather than end-running the entire process.
I think you are so missing the point. I'm not sure what point you are trying to make here, but remember that systemd is a work in progress (and some if subscribe to [systemd-dev]); as Felix noted (Message-ID: <51FFCD7D.6070101@earthlink.net>, Date: Mon, 05 Aug 2013 12:06:21 -0400) Fedora 19 has converted the /etc/init.d scripts to system .service units. Perhaps he'll tell us about the dependencies there :-) In my opinion, and I think there is a subtext in the documentation at the threads at 0pointer.de that has led me to this, that the auto-generation of units based on scripts in /etc/init.d is a kludge pending the creation of proper unit files. Please do not think that there is only the one auto-generator. Try "man 8 systemd-fstab-generator" There's a reference there to http://www.freedesktop.org/wiki/Software/systemd/Generators The last item there says <quote> Instead of heading off now and writing all kind of generators for legacy configuration file formats, please think twice! It's often a better idea to just deprecate old stuff instead of keeping it artificially alive. </quote> and I think that applies in this case; its better to create proper smb.service and nmb.service as F19 has done that rely on a generator parsing /etc/init.d files. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/5/2013 11:25 AM, Anton Aylward wrote:
John Andersen said the following on 08/05/2013 01:31 PM:
Then, circling around to the original problem, that if smb or nmb failing to start, does it make more sense to set up one's own smb.service than to fix the problem in the auto generation engine?
It would seem that if opensuse is going to continue to use auto generation that the wisest fix would be to fix that, rather than end-running the entire process.
I think you are so missing the point. I'm not sure what point you are trying to make here,
In my opinion, and I think there is a subtext in the documentation at the threads at 0pointer.de that has led me to this, that the auto-generation of units based on scripts in /etc/init.d is a kludge pending the creation of proper unit files.
You think I'm missing the point and have no idea what my point is, then you proceed to directly answer the question about the autogeneration based on init.d scrips being a kludge. (Is it against your religion to answer a direct question without first preceding it with an insult?) Without some indication by opensuse as to their plans for the future, building custom systemd scripts is likely to cause as many problems as it will solve. Why not fix the sources used by the generators in the current version(s) and wait for formal release of the non-generator version of OS. (Aren't you the one always berating Linda for the degree to which she customizes her system?) Buy the wya, Your own source suggests generators are ok in his pet case: "Generators should only be used to generate unit files, not any other kind of configuration. " -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen said the following on 08/05/2013 02:47 PM:
You think I'm missing the point and have no idea what my point is, then you proceed to directly answer the question about the autogeneration based on init.d scrips being a kludge.
(Is it against your religion to answer a direct question without first preceding it with an insult?)
So: I think you're missing my point and I think that I'm missing your point? How is saying so an insult?
Without some indication by opensuse as to their plans for the future, building custom systemd scripts is likely to cause as many problems as it will solve.
That's a perfectly valid view but I'm not sure we are going to get an answer to that. In the mean time we need to get what we have working. In my case that mean customizing units. In the future I expect it will continue to mean customization as the 'on size fits all' isn't going to fit me, nor do I think it will fit many others. In Istvan's case getting Samba to work right now has, I suspect, a higher priority than what might or might not be in some future release. If Istvan understands what is going on with systemd & samba as I've tried to explain, and perhaps if Felix sends him the F19 unit files, and he sees how they fit in and replaces the /etc/init.d scripts, then that knowledge will equip he to deal with some hypothetical but as yet unstated plan in a future openSuse release. Compared to scripting, the declarative form of the unit files is amazingly simple.
Why not fix the sources used by the generators in the current version(s) and wait for formal release of the non-generator version of OS. (Aren't you the one always berating Linda for the degree to which she customizes her system?)
The reason for not fixing the generators is that replacing the relevant scripts with .service unit files is quicker, easier, more stable and is the direction things are going - as evidenced by F19. It doesn't require knowledge of C programming, compiling etc. KISS and all that. Unlike Linda's customization this is in keeping with the direction of evolution. And as I say, it is a simplification.
Buy the wya, Your own source suggests generators are ok in his pet case: "Generators should only be used to generate unit files, not any other kind of configuration."
Once again my opinion is that you don't get it. Or perhaps you're simply being argumentative. "Pet case"? Conversion of a table to unit files - /etc/fstab or the ttys - is much more straight forward, true, but the whole point is that generating anything except unit files isn't going to be of much use at this point in the boot sequence. In an hypothetical system we could do without /etc/init.d, /etc/fstab and much else and have everything predefined as unit files. I don't know about your opinion of such a configuration but I'd hate that. There are many things that are easier to maintain as text tables such as /etc/fstab than as a long list of separate files. There are principles of keeping like things together. Yes, I'm aware of the change from the single file table of the old InetD to the multiple files of XInetD. That made me wonder, but at least they were few in number. Compare # systemctl -a | wc -l 250 And many of those are auto-generated. I'd hate t have to maintain all those as discrete files by hand. With the auto-generator many of them they are created, used and disposed of. Auto-generators have their place, but using them to deal with items in /etc/init.d that are yet to be converted is a kludge, and one that we should overcome. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
John Andersen said the following on 08/05/2013 02:47 PM:
You think I'm missing the point and have no idea what my point is, then you proceed to directly answer the question about the autogeneration based on init.d scrips being a kludge.
(Is it against your religion to answer a direct question without first preceding it with an insult?)
These religious discussions can get so ... conservative. Did anyone bother to ask the OP if there were any log files under /var/log that had the string nmb in them? or nmbd or "/nmbd?". how about asking if he tried running nmbd by hand? as root and seeing if that gives any messages to the console?
So: I think you're missing my point and I think that I'm missing your point? How is saying so an insult?
Oh yeah, well your momma dresses you guys funny! (just saying hi!)...:-) Hey, if push comes to shove, I could always send him one of my startup scripts...and some automation process could try automating it again... At least my suse system is mostly stable (i'm not installing new updates right now :-))... My win7 desktop system is another matter... damn MS updates... sure did a number on my system ...*ouch*... but my suse server... is being pretty good right now...all things considered. From unpacking the kernel & delivering file systems and logon prompt -- 34 seconds. Still have a few odd errors like: <27>[ 11.373036] udevd[858]: failed to execute '/usr/lib/udev/socket:/org/kernel/dm/multipath_event' 'socket:/org/kernel/dm/multipath_event': No such file or directory --- but they don't seem to mean anything useful that I can tell (I have no multipath devices!) Anyway, it might be a nmb config prob if his smbd is starting? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/05/2013 07:22 AM, Istvan Gabor wrote:
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
Yes, this is/was a bug in openSUSE samba packages, upstream has systemd units included but the packages don't. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez said the following on 08/06/2013 01:42 AM:
On 08/05/2013 07:22 AM, Istvan Gabor wrote:
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
Yes, this is/was a bug in openSUSE samba packages, upstream has systemd units included but the packages don't.
That's clear from Felix's observation about them being present in F19. Perhaps he would care to give details. -- "To know that we know what we know, and that we do not know what we do not know, that is true knowledge." -- Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2013-08-06 at 07:24 -0400, Anton Aylward wrote:
Cristian Rodríguez said the following on 08/06/2013 01:42 AM:
On 08/05/2013 07:22 AM, Istvan Gabor wrote:
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
Yes, this is/was a bug in openSUSE samba packages, upstream has systemd units included but the packages don't.
That's clear from Felix's observation about them being present in F19. Perhaps he would care to give details.
Hi fwiw, here's the one from the 4.0.8 source: [Unit] Description=Samba NMB Daemon After=syslog.target network.target [Service] Type=forking PIDFile=/run/nmbd.pid EnvironmentFile=-/etc/sysconfig/samba ExecStart=/usr/sbin/nmbd $NMBDOPTIONS ExecReload=/usr/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target I think the OP's problem is that the network isn't running when nmb is called. Try sticking it in /etc/init.d/boot.local perhaps? Almost certain the network is up by then. hth L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn said the following on 08/06/2013 07:46 AM:
On Tue, 2013-08-06 at 07:24 -0400, Anton Aylward wrote:
Cristian Rodríguez said the following on 08/06/2013 01:42 AM:
On 08/05/2013 07:22 AM, Istvan Gabor wrote:
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
Yes, this is/was a bug in openSUSE samba packages, upstream has systemd units included but the packages don't.
That's clear from Felix's observation about them being present in F19. Perhaps he would care to give details.
Hi fwiw, here's the one from the 4.0.8 source:
[Unit] Description=Samba NMB Daemon After=syslog.target network.target
[Service] Type=forking PIDFile=/run/nmbd.pid EnvironmentFile=-/etc/sysconfig/samba ExecStart=/usr/sbin/nmbd $NMBDOPTIONS ExecReload=/usr/bin/kill -HUP $MAINPID
[Install] WantedBy=multi-user.target
I think the OP's problem is that the network isn't running when nmb is called. Try sticking it in /etc/init.d/boot.local perhaps? Almost certain the network is up by then.
No, don't put that (the above) in /etc/init.d/boot.local - its a unit file not a script, it goes in /etc/systemd/system/ Yes, if the network isn't up, then the unit file as above makes it very clear with the "After=" line that the network is necessary. One point remains: what about smbd? Is that dependent on nmbd running? Which should start first? Oh, and a 'Spanish inquisition' point: presumably "$NMBDOPTIONS" comes from somewhere like /etc/sysconfig/nmbd ... -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Aug 06, 2013 at 07:57:56AM -0400, Anton Aylward wrote:
lynn said the following on 08/06/2013 07:46 AM: [ <8 ]
fwiw, here's the one from the 4.0.8 source:
[Unit] Description=Samba NMB Daemon After=syslog.target network.target
[Service] Type=forking PIDFile=/run/nmbd.pid EnvironmentFile=-/etc/sysconfig/samba ExecStart=/usr/sbin/nmbd $NMBDOPTIONS ExecReload=/usr/bin/kill -HUP $MAINPID
[Install] WantedBy=multi-user.target
I think the OP's problem is that the network isn't running when nmb is called. Try sticking it in /etc/init.d/boot.local perhaps? Almost certain the network is up by then.
No, don't put that (the above) in /etc/init.d/boot.local - its a unit file not a script, it goes in /etc/systemd/system/
Yes, if the network isn't up, then the unit file as above makes it very clear with the "After=" line that the network is necessary.
One point remains: what about smbd? Is that dependent on nmbd running? Which should start first?
nmbd is legacy and not a must have. That's why the smb init script has a Should-Start to the nmb service.
Oh, and a 'Spanish inquisition' point: presumably "$NMBDOPTIONS" comes from somewhere like /etc/sysconfig/nmbd ...
EnvironmentFile=-/etc/sysconfig/samba as quoted before. For SUSE we're able to reuse the existing upstream files from packaging/systemd/ Submit request against network:samba:STABLE/samba in the OBS are always welcome. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Tue, 2013-08-06 at 14:49 +0200, Lars Müller wrote:
Submit request against network:samba:STABLE/samba in the OBS are always welcome.
Hi everyone Let's help the OP and do the theory later. He said: 'How can I fix this?' My suggestion: Add the line: nmbd to /etc/init.d/boot.local Cheap and cheerful. It may get him started. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2013. augusztus 6. 17:29 napon lynn <lynn@steve-ss.com> írta:
On Tue, 2013-08-06 at 14:49 +0200, Lars Müller wrote:
Submit request against network:samba:STABLE/samba in the OBS are always welcome.
Hi everyone Let's help the OP and do the theory later. He said: 'How can I fix this?'
My suggestion: Add the line: nmbd to /etc/init.d/boot.local
Cheap and cheerful. It may get him started. L x
Thank you all for your hints. Currently I am away from the affected computer. When I get back to it I will try to fix the problem and will report how it went. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2013. augusztus 6. 17:29 napon lynn <lynn@steve-ss.com> írta:
On Tue, 2013-08-06 at 14:49 +0200, Lars Müller wrote:
Submit request against network:samba:STABLE/samba in the OBS are always welcome.
Hi everyone Let's help the OP and do the theory later. He said: 'How can I fix this?'
My suggestion: Add the line: nmbd to /etc/init.d/boot.local
Cheap and cheerful. It may get him started. L x
Hello: I have added the line nmb (not nmbd) to /etc/init.d/boot.local. This fixed the startup of the demon at boot. Thanks! Previously I also tried the .service scripts. I downloaded the samba src.rpm file from opensuse site, and extracted the nmb.service, smb.service and winbind.service files from it. I copied these files into /etc/systemd/system directory. This did not help. nmb did not start and even the starting of smb was prevented/disabled. What should I do if I wanted to start nmb through the script and not by the boot.local? I'm just curious. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 24 Aug 2013 11:37:13 +0200 Istvan Gabor <suseuser04@lajt.hu> пишет:
Previously I also tried the .service scripts. I downloaded the samba src.rpm file from opensuse site, and extracted the nmb.service, smb.service and winbind.service files from it. I copied these files into /etc/systemd/system directory.
This did not help. nmb did not start and even the starting of smb was prevented/disabled.
What should I do if I wanted to start nmb through the script and not by the boot.local?
Just like in the sysvinit case, you need to explicitly configure it to be started during boot. Think of /etc/systemd/system as of /etc/init.d. Having script there is not enough to make script run on startup; you also need to link it in proper "run-level". If service file has correct [Install] section, you can do it using "systemctl enable nmbd.service" (similar to chkconfig nmbd on). If service file does not have [Install] section, you can manually link it into /etc/systemd/system/default.target.wants (or multi-user.target.wants) so that service is started wherever you boot. Again, this is exactly the same with sysvinit scripts lacking meta information for chkconfig - you manually link into respective /etc/init.d/rc?.d directory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 2013-08-06 at 07:57 -0400, Anton Aylward wrote:
No, don't put that (the above) in /etc/init.d/boot.local - its a unit file not a script, it goes in /etc/systemd/system/
lol, no. Try nmbd instead;) L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-08-06 07:24 (GMT-0400) Anton Aylward composed:
Cristian Rodríguez wrote:
Istvan Gabor wrote:
2. I could not find any *.service file containing strings 'smb' or 'nmb' on my whole system. (Starting search in the / directory.)
Yes, this is/was a bug in openSUSE samba packages, upstream has systemd units included but the packages don't.
That's clear from Felix's observation about them being present in F19. Perhaps he would care to give details.
What details? FWIW, installing samba-server on Mageia 3 (released after 12.3) reports "smb.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig on." Searching its / produces no hits for ?mb*vice. Chkconfig --list shows only smb, no nmb. ISTR no nmb similarly elsewhere over the years. Why is nmb ever a separate service from smb? Is one ever needed without the other too? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrey Borzenkov -
Anton Aylward -
Cristian Rodríguez -
Felix Miata -
Istvan Gabor -
John Andersen -
Lars Müller -
Linda Walsh -
lynn