[chef] Client locking

[Douglas Garstang < >]

I'm starting new instances, and the chef clients starts on boot from init. I'm then stopping it (service chef-client stop), and running it manually so that I can get a better idea of what's going on. I recently added the chef-client to the runlist, and ocassionally duing the foreground run, the client barfs with locking errors (from yum). This would tend to indicate to me that the client started from the recipe is trying to run while the client is also running in the foreground.

I thought I had seen in the past where, if the client was actually running (not just running as a daemon) that running it on the foreground would tell the client was already running and stop.

Bottom line... does the client have locking? What happens if it's doing a foreground run and the daemon kicks off a parallel run?

Doug