On Fri, Jan 29, 2010 at 05:11:29AM +0100, Håkan Johansson wrote:
> >In the latest git the permissions can now be specified with :perm=666.
>
> Great!
>
> Perhaps and the output of strtol(s, NULL, 8) with 0666 to prevent
> the user from setting any other flags by mistake.
Good idea. Thanks.
--
In the latest git the permissions can now be specified with :perm=666.
Great!
Perhaps and the output of strtol(s, NULL, 8) with 0666 to prevent the
user from setting any other flags by mistake.
Cheers,
Håkan
On Tue, Jan 26, 2010 at 12:54:45PM +0100, Håkan Johansson wrote:
>
> Ok, could it perhaps be made an explicit option of the refclock?
> (The sysadmins were happy to not have to change more than the config
> file for the few machines in question. :) )
In the latest git the permissions can now be
On Tue, Jan 26, 2010 at 12:54:45PM +0100, Håkan Johansson wrote:
>
> Ok, could it perhaps be made an explicit option of the refclock?
I think that would be ok. We don't have a mechanism for passing
arbitrary options to drivers, but maybe colons could be used in
refclock parameter, e.g "refclock
Ok, could it perhaps be made an explicit option of the refclock? (The
sysadmins were happy to not have to change more than the config file for
the few machines in question. :) )
Cheers,
Håkan
On Tue, 26 Jan 2010, Miroslav Lichvar wrote:
On Mon, Jan 25, 2010 at 09:48:57PM +0100, Håkan
On Mon, Jan 25, 2010 at 09:48:57PM +0100, Håkan Johansson wrote:
> On Mon, 25 Jan 2010, Bill Unruh wrote:
> >I am not sure that this is a good idea, since this would allow anyone to send
> >rogue data to the shm driver. It would be better to leave it at 0600 for the
> >chrony user ( or for root if
On Mon, 25 Jan 2010, Bill Unruh wrote:
I am not sure that this is a good idea, since this would allow anyone to send
rogue data to the shm driver. It would be better to leave it at 0600 for the
chrony user ( or for root if you are using root), and let root change it if
the sysadmin wants to
Hi,
ntpd creates the shm refclock segments 2 and 3 with permissions 0666
(previously 0777), allowing also non-root users to provide synchronisation
data when these segments are set up. The attached patch changes chrony to
do that to (currently 0700 for all segments). It also changes the
I am not sure that this is a good idea, since this would allow anyone to send
rogue data to the shm driver. It would be better to leave it at 0600 for the
chrony user ( or for root if you are using root), and let root change it if
the sysadmin wants to allow anyone to write to the shm, or at most
