>Is there anything left to do before 1.24?
>
>If there are no bugreports, I'd like to make the release next week.
I will run chrony on a few systems over the weekend but so far I
haven't seen any bugs. I'll let you know my results next Tuesday.
--
Tjalling Hattink
---
To unsubscribe email
Is there anything left to do before 1.24?
If there are no bugreports, I'd like to make the release next week.
--
Miroslav Lichvar
---
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with
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.
--
This is an automated email from git. It was enerated because a ref
change was pushed to the repository "chrony/chrony.git".
The branch, master has been updated
via a123a12f593679bfc400ae72155dccee3d21209c (commit)
from f261251a9bcee1acc233e7fb96f841a60bb83b2a (commit)
Those
On Fri, 29 Jan 2010, Miroslav Lichvar wrote:
Is there anything left to do before 1.24?
If there are no bugreports, I'd like to make the release next week.
One minor bug report-- the chown of the rtc and drift files leaves hundreds of
messages in syslog
Jan 24 04:03:13 info chronyd[4328]:
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
