I'm trying to run pwck with Puppet 2.6.4. pwck checks the passwd file
and makes sure that, for example, each user's home directory exists.
(And other stuff.) When everything is OK, it doesn't say anything. So if
it says something, I want to know it, and I want it to stand out from
other exec output
On Mon, 06 Jun 2011 09:37:48 -0500, Jennings, Jared L CTR USAF AFMC 46 SK/CCI
wrote:
>
> I'm trying to run pwck with Puppet 2.6.4. pwck checks the passwd file
> and makes sure that, for example, each user's home directory exists.
> (And other stuff.) When everything is OK, it doesn't say anything
Helwig:
> Unfortunately, the documentation is just plain wrong. loglevel is the
> only one that supports "any legal log level". logoutput really does
> only support true, false, and on_failure.
>
> Is pwck exiting non-zero when there is output? That should be
> sufficient to trigger the behavio
On Tue, 07 Jun 2011 10:29:12 -0500, Jennings, Jared L CTR USAF AFMC 46 SK/CCI
wrote:
>
> Helwig:
> > Unfortunately, the documentation is just plain wrong. loglevel is the
> > only one that supports "any legal log level". logoutput really does
> > only support true, false, and on_failure.
> >
>
Helwig:
> On Tue, 07 Jun 2011 10:29:12 -0500, Jennings, Jared L CTR USAF AFMC 46
> SK/CCI wrote:
> > pwck indeed behaves nicely with its exitcodes - the problem is I
want
> > the output to be an err, not a notice
>
> exec { 'pwck -r':
> path => '/usr/bin:/bin:/usr/sbin:/sbin',
> log
