On Tue, Nov 8, 2011 at 12:21, Bob Proulx <b...@proulx.com> wrote: >> from this I was able to determine that NSCD wasn't running, restarting >> this allowed jobs to run successfully! > > Does this mean that you are running NIS/YP or LDAP from the network? > Are your servers "slow" such as on a remote network or otherwise > negatively impacting performance?
They shouldn't that are on the same subnet and linked via 10GigE. > If not then I wouldn't run nscd at all. I have run into problems with > its caching implementation. Secondary account entries override > primary ones (the opposite of desired) when running nscd for example. > And the daemon sometimes stops running, as you just found. If you > don't need it then it is better not to run it and it is rare to find > people who really need it these days. Without NSCD running cron jobs fail to run, if you're suggesting not running it how can I get cron working? Cheers Adam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+mfgz2b0u_jm66-ot5esqstnqyk5axpwvyg32nenecxl_3...@mail.gmail.com
