Puppet users - Aug 2010 - Using "service" with a specific user

Hi !

I would like to use the type "service" to ensure that a service is
currently started. Is there a way to specify a user that must run
start or stop command ?

In the same way that "exec".

Regards,
Matt

-- 
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.

Matt <matthieu.nantern@gmail.com> writes:
> I would like to use the type "service" to ensure that a service
is currently
> started. Is there a way to specify a user that must run start or stop
> command?
No.  Traditionally, the start and stop commands would ensure that the software
ran as the correct user internally — most of them map directly to the OS
facilities that start and stop services at boot time, which require that.

I would strongly advise you follow that same path, because otherwise you
risk a tiny typo or user-error resulting in your daemon running as root.

        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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.

The way you make the service start/stop by a specific user is to make sure
the OS-standard start/stop script do su/sudo at the correct point.

On Mon, Aug 30, 2010 at 6:43 AM, Daniel Pittman <daniel@rimspace.net>
wrote:
> Matt <matthieu.nantern@gmail.com> writes:
>
> > I would like to use the type "service" to ensure that a
service is
> currently
> > started. Is there a way to specify a user that must run start or stop
> > command?
>
> No.  Traditionally, the start and stop commands would ensure that the
> software
> ran as the correct user internally — most of them map directly to the OS
> facilities that start and stop services at boot time, which require that.
>
> I would strongly advise you follow that same path, because otherwise you
> risk a tiny typo or user-error resulting in your daemon running as root.
>
>        Daniel
> --
> ✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155
> 707
>               ♽ made with 100 percent post-consumer electrons
>
> --
> 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<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
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.

Brian Gallew <geek@gallew.org> writes:

G''day Brian.

The mechanism for ensuring your software runs with the right privileges
actually varies a lot: some providers (like launchd) handle that internally,
other platforms (like Debian) provide specific tools to do it.

Additionally, many applications integrate this support, especially tools that
require some period of execution with elevated privileges (like Apache).

However, for writing your own scripts the use of su or sudo can be effective;
my personal preference is to use a tool like daemon[1] that wraps up a whole
lot of the things that su doesn''t for starting a daemon.

Regards,
        Daniel
> The way you make the service start/stop by a specific user is to make sure
the
> OS-standard start/stop script do su/sudo at the correct point.
>
> On Mon, Aug 30, 2010 at 6:43 AM, Daniel Pittman <daniel@rimspace.net>
wrote:
>
>> Matt <matthieu.nantern@gmail.com> writes:
>> 
>> > I would like to use the type "service" to ensure that a
service is
>> currently > started. Is there a way to specify a user that must run
start or
>> stop > command?
>> 
>> No.  Traditionally, the start and stop commands would ensure that the
>> software ran as the correct user internally — most of them map directly
to
>> the OS facilities that start and stop services at boot time, which
require
>> that.
>> 
>> I would strongly advise you follow that same path, because otherwise
you
>> risk a tiny typo or user-error resulting in your daemon running as
root.
>> 
>>        Daniel -- ✣ Daniel Pittman            ✉ daniel@rimspace.net    
     
>>  ☎ +61 401 155 707               ♽ made with 100 percent post-consumer
>> electrons
>> 
>> -- 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.
>> 

Footnotes: 
[1]  http://www.libslack.org/daemon/

-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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.