----- Original Message ----- > Thanks for the reply. > > > I modified the rc script to run as a user. > But now I'm facing the following problem: > I have to include some nasty puppet code for adding the service > before i can use the service resource type. > And the service resource type returns ok, but the service is in fact > not started. > When i do it manually, it requires a password for that user. > So, I tried to manage the user with puppet and provided a password, > but get the message: > Provider useradd does not support features manages_passwords; not > managing attribute password > I know this is a problem with Puppet and CentOS, but I have > ruby-shadow and shadow-utils installed on my CentOS 6.0 VM. > > > I also don't know if this is going to help with starting the service. > I want to use the service type to start the service with a specific > user, but without asking for a password.
you should use su in your script to switch users to the one the service should run as. consider what will happen when your server starts up? the rc script runs and then what? ask you for a password? thats not good. the rc script has to do what it should without interaction, its not a puppet problem. all you should need to do is copy the working rc script into the init.d dir and use the service resource to enable it and ensure its running. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
