I should note that this or a similar problem is noticeable on Debian
Lenny - ie, high CPU usage by samba. This may or may not be related to
CUPS on Debian: restarting samba alone doesn't fix it on the debian
machine, but restarting cups -then- samba does.
I've not noticed the problem in Ubuntu 9.0
Janaka - I would suggest going into /etc/rc#.d and moving the S20samba
to K20samba, if you have not done so already. This should stop samba
from starting on boot.
--
nmbd -D uses 95% processor when there is not lan conection.
https://bugs.launchpad.net/bugs/292548
You received this bug notificati
This bug is easily reproducible with a fairly stock Ubuntu install of
Samba if one switches networks.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
nmbd -D uses 95% processor when there is not lan conection.
https://bugs.launchpad.net/bugs/292548
You received this bug notifica
I seem to repeatedly trigger this bug, just in my house (laptop w/
wifi/ethernet, on Ubuntu 8.10, samba package 2:3.2.3-1ubuntu3.4). It
happens if the interface itself is lost, and it -may- also happen if the
IP is unassociated - I believe it depends on how your samba is
configured (subnet vs. inte
