Hal Murray via devel :
> Has anybody noticed anything similar? Are you running the latest bits? ...
I thought I was, but I could be wrong. I haven't seen anything untoward.
--
http://www.catb.org/~esr/";>Eric S. Raymond
My work is funded by the Internet Civil Engineering Insti
Hal Murray via devel :
> How do other projects with similar name clashes handle things?
They don't.
Distro packagers check for these sorts of collisions and declare
packages to be "conflicting" when they're found. Comnflicting
pacjages may be registered as "alternatives" in which case the packag
> That works only because we install in /usr/local/ while the system
version of
> ntp classic gets installed in /usr/ What's going to happen if a distro
> packages up our stuff and somebody wants to install both our code and ntp
> classic?
For a distro, like Debian, the new package would be calle
Poking around, I see that some of my servers are not responding. (I test
various combinations and/or collect data with noselect.)
Has anybody noticed anything similar? Are you running the latest bits? ...
I haven't seen any problems recently so I assume it's due to a recent change.
All my
We have ntpd and ntpq that replace the programs with the same names from ntp
classic.
For testing, we install in /usr/local/ so we don't conflict with a system
version of ntp classic. If you hack your search path, you get our code
rather than the system programs with the same names.
That wor
Where is the documentation that tells somebody what they have to do on their
system if they want to use our code?
I'm expecting that to be partly a general overview and partly small diffs for
each distro/release to document the details. or at least one set of working
details.
--
These are my
Yo Achim!
On Fri, 16 Feb 2018 21:21:04 +0100
Achim Gratz via devel wrote:
> Gary E. Miller via devel writes:
> >> You don't need root for /dev/whatever if you set the owner to
> >> ntp:ntp before starting ntpd.
> >
> > Which of course, you have to every time you reboot. And since most
> > peo
Yo Hal!
On Fri, 16 Feb 2018 12:17:26 -0800
Hal Murray wrote:
> >> Config in /etc/ntpsntp.conf
> > /etc/ntpsntpd.conf server, not client.
>
> Interesting.. Thanks.
>
> ntpd is both client and server. We don't use the "d" on config files.
Old bug. What NTPsec client uses /etc/ntp.conf?
>
On 02/16/2018 02:17 PM, Hal Murray via devel wrote:
Is there a client for ntpsnmpd? I'd expect the client side to be part
of a snmp package. Do we need samples for that? How many snmp packages
are there?
ntpsnmpd only talks to the snmpd daemon. Various sorts of clients,
including the tools
Gary E. Miller via devel writes:
>> You don't need root for /dev/whatever if you set the owner to ntp:ntp
>> before starting ntpd.
>
> Which of course, you have to every time you reboot. And since most
> people now use udevd, it needs a rule change.
No, that's what udev does for you if you ask it
>> Config in /etc/ntpsntp.conf
> /etc/ntpsntpd.conf server, not client.
Interesting.. Thanks.
ntpd is both client and server. We don't use the "d" on config files.
Is there a client for ntpsnmpd? I'd expect the client side to be part of a
snmp package. Do we need samples for that? How many
Yo Hal!
On Fri, 16 Feb 2018 11:55:59 -0800
Hal Murray wrote:
> The initial message was asking if there was any interest. (Or
> implicitly, any objections.) I wasn't going to polish things like
> documentation if somebody pointed out a fatal flaw.
The bias against letting 'mere users' touch ro
devel@ntpsec.org said:
> You know our users do not read man pages! Can you provide a script, or at
> least a detailed procedure?
Sure. If you look back in the message that started this thread there are
snippets of code.
The initial message was asking if there was any interest. (Or implicitl
Yo Hal!
On Fri, 16 Feb 2018 11:42:30 -0800
Hal Murray via devel wrote:
> devel@ntpsec.org said:
> > There are two sets of configuration data: the usual server and
> > logging settings, and the flags which control which notifications
> > are active.
>
> I'd put stuff in parallel with ntp/ntpd
devel@ntpsec.org said:
> There are two sets of configuration data: the usual server and logging
> settings, and the flags which control which notifications are active.
I'd put stuff in parallel with ntp/ntpd
Config in /etc/ntpsntp.conf
State to be saved over boot in /var/ntpsntp/
Cleaned over b
Address mixup landed this in my inbox instead of the devlist. Forwarding
so that it becomes part of the discussion.
Forwarded Message
Subject:Re: ntpsnmpd beta
Date: Fri, 16 Feb 2018 09:30:19 -0800
From: Gary E. Miller
Organization: Rellim
To: Ian Bruene
On 02/16/2018 01:09 PM, Eric S. Raymond wrote:
Ian Bruene via devel :
Query: what file can/should I use for config data that ntpsnmpd needs to be
able to change on the fly?
Does a human ever set this data? If not, there's a (weak) convetion of
putting the file in /var/run.
There are two se
Ian Bruene via devel :
> Query: what file can/should I use for config data that ntpsnmpd needs to be
> able to change on the fly?
Does a human ever set this data? If not, there's a (weak) convetion of
putting the file in /var/run.
--
http://www.catb.org/~esr/";>Eric S. Raymond
M
Yo Hal!
On Thu, 15 Feb 2018 19:55:02 -0800
Hal Murray wrote:
> > Doesn't ntpd need to be started as root to set that?
> > But how does ntpd set its caps before it starts?
>
> man 8 setcap
You know our users do not read man pages! Can you provide a script,
or at least a detailed procedure?
Query: what file can/should I use for config data that ntpsnmpd needs to
be able to change on the fly?
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave Obeys."/ -- Andrew Ryan
/"Utopia cannot precede the Utopian. It will exist the moment we are f
MIB implementation complete except for where explicitly not implemented.
No known bugs extant, mostly due to lack of swarm attack.
Packet handling implemented for all required PDU types. But not all in
general.
Can has testers?
--
/"In the end; what separates a Man, from a Slave? Money? Pow
21 matches
Mail list logo