Re: Logfile permissions and ntp group

Yo Hal! On Tue, 07 Jun 2016 16:51:05 -0700 Hal Murray wrote: > g...@rellim.com said: > > logrotate does not make files, it restarts ntpd, so ntpd can make > > the new file. Which has all the problems of restarting ntpd. > > The logrotate I'm familiar with has the

Re: Logfile permissions and ntp group

g...@rellim.com said: > logrotate does not make files, it restarts ntpd, so ntpd can make the new > file. Which has all the problems of restarting ntpd. The logrotate I'm familiar with has the option to make the new file after renaming the old one. (I may be confused by the netbsd/freebsd

Re: Logfile permissions and ntp group

Hal Murray : > The stats files automatically roll over. You can specify how often, but > daily works for me. They don't get opened until needed which is long after > dropping root, so they need the right user:group on the directory as well as > any existing current

Re: Logfile permissions and ntp group

Yo Hal! On Tue, 07 Jun 2016 16:17:38 -0700 Hal Murray wrote: > e...@thyrsus.com said: > > You are suggesting that this is not so - that as long as we open > > log files before privilege-dropping the ntp user/group pair isn't > > necessary at all. If true I would mildly

Re: Logfile permissions and ntp group

Yo Eric! On Tue, 7 Jun 2016 18:46:44 -0400 "Eric S. Raymond" wrote: > I thought I was going to have to tweak clockmaker to create an ntp > user and group if it doesn't already exist, then set ntp to run with > those IDs in the init script. That's easy enough to do. And

Re: Logfile permissions and ntp group

On 06/07/2016 06:46 PM, Eric S. Raymond wrote: Mike : On 06/07/2016 05:57 PM, Hal Murray wrote: Ntpd is running as user nobody, whom can't write to that directory. Hopefully that is user ntp rather than nobody. The file permissions need to be setup for log files as well