On Wednesday, October 10, 2012 7:08:21 AM UTC-5, Sean Millichamp wrote:
>
> Tom,
>
> It seems like having that as a parameter in the service type might be a
> good idea worthy of at least some further discussion.
"[T]hat" refers to an SELinux context in which the service management
commands
Tom,
It seems like having that as a parameter in the service type might be a
good idea worthy of at least some further discussion. Want to open a
feature request in Redmine to track it? I might (eventually) take a stab
at adding support for it.
Sean
On Wed, 2012-10-10 at 09:01 +0100, Tom wrote:
Well, I've decided on a very simple way of doing this,
# Keep it running
service { "mysqld":
ensure => "running",
start => "runcon -u system_u /etc/init.d/mysqld start",
hasrestart => "false",
require=> [ Package["mysql-server"], File[$mysqldirs], ],
}
so, it s
Hi,
Thanks for the response. Really, I think the way I'm approaching this
is thinking about starting mysqld under the right selinux user context
so that it doesn't label its own files incorrectly. Every time a
database or table is created, MySQL will be creating it under the wrong
user cont
You need to add a require to the service for the config files you are managing.
I find the best way to do that is put all the config files in a config
subclass and then require that in in the service.
On 10 October 2012 01:02, Tom wrote:
> Hi list,
>
> I've got an issue at the moment, which isn'
Hi list,
I've got an issue at the moment, which isn't really a big problem, but
an untidy annoyance really, and I'd just like to understand what the
best practice might be when dealing with the issue.
As a really quick summary, the issue is that Puppet is starting up the
mysqld service for t
