No, not even the fix. I might have to look deeper into it. It's too bad,
that this bug is that old.
Samba 4 is really great. Once installing and compiling by hand under
Ubuntu it really rocks. I'm pretty sure there is a lot of mess with the
packages patches and old scripts. We should find a way to
Well, his fix did not work. Let's try the sleep hack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1078699
Title:
winbind won't start at boot
To manage notifications about this bug
Using Ubuntu 14.04.1 LTS. I also have this bug ans as Clint Byrum
(clint-fewbar) writes with lsb-init scripts I have to agree. I don't
understand everything but I have the old settings and changed them now.
Rebooting the system. Let's see if winbind and nmbd are loaded...
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/107869
** Changed in: samba (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1078699
Title:
winbind won't start at boot
To manage notifications about
Here's a dump directly from /var/crash
Just re-run version check:
# apt-cache policy winbind
winbind:
Installato: 2:3.6.3-2ubuntu2.3
Candidato: 2:3.6.3-2ubuntu2.3
Tabella versione:
*** 2:3.6.3-2ubuntu2.3 0
500 http://it.archive.ubuntu.com/ubuntu/ precise-updates/main amd64
Package
A just slightly less ugly fix is introducing
/etc/rc2.d/S10sleep
with
RCDELAY=30
sleep $RCDELAY
Seems to work
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1078699
Title:
winbind
IIUC, winbind should be started *before* smbd, not after (smbd uses
winbind, if available, for mapping). And actually I don't have smbd
installed at all (I just use winbind to authenticate and authorize local
users against AD).
To collect crash logs I'll have to install another system: the two
aff
Ok, first off, winbind.conf has this old relic start on
start on (local-filesystems and net-device-up IFACE!=lo)
stop on runlevel [!2345]
This will start winbind as soon as *any* network interface is up, which
is not what we want. The appropriate conditions are:
start on runlevel [2345]
stop on
I don't think so, but might be (hard to tell, when speaking of race conditions).
In 1083407 winbindd is hung, while in this case it exits. And the machines
where I experienced that are actually quite slow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Possibly related to bug 1083407?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1078699
Title:
winbind won't start at boot
To manage notifications about this bug go to:
https://bugs.
11 matches
Mail list logo
