After latest update, winbind will not start, making apt stall.
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm closing this bug as the bug has been fixed in 3.0.25a-1:
- patches/fhs.patch: recreate winbindd_cache.tdb in the cache directory
instead of the lock directory.
** Changed in: samba (Ubuntu)
Status: Incomplete = Fix Released
--
winbindd will not start do to invalid cache path
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However I cannot reproduce your problem. I've setup a
domain following the Samba-3 HowTo with a Samba PDC and a Samba member
server. winbindd starts correctly on the member server and everything
works correctly.
** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Mathias Gug
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Changed in: samba (Ubuntu)
Target: ubuntu-7.10-beta = tribe-4
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Thanks a lot! It gets a bit tight for Tribe-4 now, but if someone wants
to grab this and give this a thorough test, that's fine for T4. Should
be fixed in T5 at latest, though.
** Changed in: samba (Ubuntu)
Importance: Critical = High
Target: tribe-4 = tribe-5
--
winbindd will not
This bug is critical. Winbind being unusable is not good.
** Changed in: samba (Ubuntu)
Importance: Undecided = Critical
Target: None = ubuntu-7.10-beta
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification
There is a lot of argument between the Debian packager and the Samba
team about this bug. Basically it centers around whether winbindd_cache
should be in /var/cache or not. Upstream thinks not, Debian thinks it
should be.
winbindd_cache is a cache. But it is a cache which cannot be safely
deleted
Attached is a new version of fhs.patch which fixes this.
** Attachment added: fhs.patch
http://launchpadlibrarian.net/8478423/fhs.patch
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification because you are a member of
Previous patch had some extra files. This patch has been cleaned up.
** Attachment added: fhs.patch
http://launchpadlibrarian.net/8478436/fhs.patch
--
winbindd will not start do to invalid cache path
https://bugs.launchpad.net/bugs/118977
You received this bug notification because you are a
10 matches
Mail list logo
