I have an Apparmor profile in the Debian package, which is derived from
the packaging for NTP Classic, which comes fromm Novell/SUSE with
changes by Canonical for Ubuntu. I had to make some changes to support SSL.
--
Richard
___
devel mailing list
devel
Hal Murray via devel writes:
> Has anybody played with chroot? apparmor?
openSUSE delivers both ntpd and ntpsec with apparmor profiles. The
standard profile needs a bit of editing if you set up a reference clock
in order for the daemon to get at the device files.
Regards,
Achim.
--
+<[Q+ Mat
I like the "two sets of counters" idea.
On Wed, Jun 6, 2018 at 10:18 PM Hal Murray via devel
wrote:
>
> [if (0) on debugging msyslog]
> > What I do is delete them unless I think they might have continuing
> value, in
> > which case I put them under DPRINTF.
>
> I agree on the "continuing value"
[if (0) on debugging msyslog]
> What I do is delete them unless I think they might have continuing value, in
> which case I put them under DPRINTF.
I agree on the "continuing value" part.
For what I'm after, msyslog is more convenient that DPRINTF. I'm willing to
do an edit/build/restart cycl
>> The code for freeing up key strings zeros them out first. How do we do
that in python or go?
> Same way you would in C, iterate over them writing zeros. Am I missing
something?
I may be not understanding something.
I thought that strings were non-mutatable in Python, and every time one is
wri
Hal Murray via devel :
> I occasionally add msyslog lines when debugging. The DPRINTF stuff isn't
> interesting - too much junk I don't want. When I'm cleaning up, should I
> disable them with "if (0)", or delete them? Is there a better way? ...
What I do is delete them unless I think they m
