Bug#793876: RFS: chrony/1.31.1-1

[Vincent Blut <vincent.debian@free.fr>]

Le ven. 21 août 2015 à 14:41, Jerome BENOIT <calculus@rezozer.net> a 
écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello Vincent:

Hey Jerome,

> On 20/08/15 19:20, Vincent Blut wrote:
> >  Le jeu. 20 août 2015 à 16:07, Jerome BENOIT 
> > <calculus@rezozer.net> a écrit :
> > >  -----BEGIN PGP SIGNED MESSAGE-----
> > >  Hash: SHA1
> > >
> > >  Hello Vincent:
> >
> >  Hey again Jerome,
> >
> > >  On 20/08/15 13:57, Vincent Blut wrote:
> > > >   Le jeu. 20 août 2015 à 0:31, Jerome BENOIT 
> > > > <sphericaltriangle@rezozer.net> a écrit :
> > > > >   For something as one week, the current GIT version at Aliot 
> > > > > works great on my box.
> > > > >   (even if the option -u doent work).
> > > >
> > > >   Thanks Jerome for testing! I just tried to run chrony with the 
> > > > '-u' option from
> > > >   the shell prompt, but at first glance the clock synchronizes 
> > > > flawlessly to the
> > > >   NTP server. Could you be more specific about what doesn’t 
> > > > work? Does chrony display
> > > >   any error messages?
> > >
> > >  […]
> > >  I can send this material if you want.
> >
> >  Yes please, I’ll test your configuration in a VM. Don’t know 
> > when though,
> >  I have some high priority IRL stuff to do.
>
> [snip]
>
> I also obsoleted ('^##OBSOLETED##) the code that pass the user to the 
> daemon:
> just uncommented it to test.

Well I just take a look at your init script, and it appears that that 
part is buggy. You’re
passing uid:gid values to 'chronyd -u'. The '-u' option only accept a 
username.

Thus, just drop your UGID variable, and do something like this:

if test "$(uname -s)" = "Linux"; then
	CHRONY_OPTS="$CHRONY_OPTS -u $DAEMONUSER"
fi

Also, instead of defining a variable in your init script to set the 
user with which
chronyd will be launch, I invite you to use the "user" directive in 
/etc/chrony/chrony.conf

> Best wishes,
> Jerome

Cheers,
Vincent