Puppet users - Jan 2010 - Reloading puppet client after nss change

I''m using puppet to push around nss-db updates but I''m having
problems where
the currently running puppet instance doesn''t see the new users from
the new
nss-db files until it re-executes.  This causes problems when I have modules
to create ssh authorized_keys files directly after this (the dependencies are
set up properly; puppet just can''t find the users).

Is there a way to notify puppet "you need to reload now" or something
similar
for this situation?

-Doug

Check this out:
http://groups.google.com/group/puppet-users/browse_thread/thread/23644c7a25661a2a/91b87703009f851d



Silviu


On 06.01.2010 17:35, Doug Warner wrote:
> I''m using puppet to push around nss-db updates but I''m
having problems where
> the currently running puppet instance doesn''t see the new users
from the new
> nss-db files until it re-executes.  This causes problems when I have
modules
> to create ssh authorized_keys files directly after this (the dependencies
are
> set up properly; puppet just can''t find the users).
>
> Is there a way to notify puppet "you need to reload now" or
something similar
> for this situation?
>
> -Doug
>
>    

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.