Created attachment 345692 [details] updated patch "This would be a bit too radical, while we discourage using winbind in conjunction with nscd we cannot prevent an admin that knows what he is doing from doing so." I agree, but don't we usually add an option for such a case (i.e. make the needed change but provide a way to override the new functionality?). I have attached a new patch that has such an option. Let me know if something like this will work. Also -- for the immediate future -- it could be that the default is set to allow the service to start. This would allow for normal operation to continue, but give some heads up for future changes. +++ This bug was initially created as a clone of Bug #502262 +++ Created an attachment (id=345162) a simple check for nscd in the winbind init script Description of problem: According to "http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/winbind.html#id2650352" winbind should never be started when nscd is running. I believe the winbind service should refuse to start if nscd is running. Version-Release number of selected component (if applicable): How reproducible: service nscd start service winbind start Actual results: winbind starts with nscd running Expected results: winbind should refuse to start Additional info: patch included --- Additional comment from ssorce on 2009-05-26 16:03:41 EDT --- This would be a bit too radical, while we discourage using winbind in conjunction with nscd we cannot prevent an admin that knows what he is doing from doing so.
Just for thought, at the very least a stern warning could be displayed if nscd is running. The upstream warning is worded exactly "Do not under any circumstances run nscd on any system on which winbindd is running.".
While we discourage using winbind in conjunction with nscd we cannot prevent an admin that knows what he is doing from doing so.