** Changed in: samba
Importance: Unknown => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/100019
Title:
Segfault in Samba
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Acked - it appears to catch the condition gracefully in hardy.
[2008/04/06 20:48:13, 0] nmbd/nmbd.c:main(711)
Netbios nameserver version 3.0.28a started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2008/04/06 20:48:13, 0] nmbd/nmbd_subnetdb.c:create_subnets(245)
create_subnets: u
Hello,
I believe this is fixed in hardy. If possible could you please check.
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
Segfault in Samba
https://bugs.launchpad.net/bugs/100019
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: samba (upstream)
Status: Confirmed => Fix Released
--
Segfault in Samba
https://bugs.launchpad.net/bugs/100019
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
htt
** Changed in: samba (upstream)
Status: Unknown => Confirmed
--
Segfault in Samba
https://bugs.launchpad.net/bugs/100019
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
>The smb.conf had been set to eth0, when in the new motherboard, the NIC comes
>up as eth1. This still has to be a bug; I >dont think a segfault is the
>desired behavior if an
cf /etc/iftab why it's eth1 now.
** Changed in: samba (Ubuntu)
Status: Needs Info => Confirmed
** Bug watch adde
Well, I seem to have found the problem in the process of gathering the
requested info. The smb.conf had been set to eth0, when in the new
motherboard, the NIC comes up as eth1. This still has to be a bug; I
dont think a segfault is the desired behavior if an interface becomes
unavailable, but suf
hi,
can you add:
- your /etc/samba/smb.conf if you've modified it? At least the first lines
where interfaces is set.
- var/log/nmbd.log*, if you can try to find output with the same date than the
core it'd be great (maybe around 7 AM ?)
>From the source there's actually a bug in nmbd if no wor
