Mailinglist Archive: opensuse (1420 mails)

< Previous Next >
Re: [opensuse] multiboot value

On Tue, Jan 21, 2014 at 12:12:10PM -0800, John Andersen wrote:
On 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if
11.4 had never had a problem seeing or being seen in the first

I often run into the exact same problem, and simple take down and bring up
I've always liked the ability to do that separate from smbd, because it
doesn't disrupt
existing user connections. However it seems in later releases, smbd and nmbd
are managed
in parallel and are harder to manage separately.

That's more or less still the same. Independent if we use native
systemd service files or not.

hip:~ # systemctl status nmb.service
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled)
Active: inactive (dead)

Jan 18 18:25:13 hip systemd[1]: Stopped Samba NMB Daemon.
Jan 18 18:27:18 hip systemd[1]: Stopped Samba NMB Daemon.

Here you see nmbd is inactive.

hip:~ # systemctl status smb.service
smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled)
Active: active (running) since Mo 2014-01-20 15:20:13 CET; 1 day 18h
Main PID: 24854 (smbd)
CGroup: /system.slice/smb.service
├─24854 /usr/sbin/smbd -D
└─24855 /usr/sbin/smbd -D

Jan 20 15:20:13 hip systemd[1]: Started Samba SMB Daemon.

Instead of the status command you're ale tu use start, stop, enable,
disable, is-enabled, and so on. See the systemctl man page for all the

Forcing an election doesn't always work. (That happens every time a new
station comes on
line anyway).

Is AppArmor active?

Are you able to pin it down to a particular Samba or SUSE version when
it still worked and when it got broken?

Please consider to file a bug report and include the ID in your reply to
this thread.


Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team + SUSE Labs
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
< Previous Next >
Follow Ups