ntpd says it's pidfile is in /var/run, when it should be in /run.
--
Nathan Coulson (conathan)
--
Location: British Columbia, Canada
Timezone: PST (-8)
Webpage: http://www.nathancoulson.com
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq
On Mar 21, 2012, at 1:33 AM, Nathan Coulson wrote:
> ntpd says it's pidfile is in /var/run, when it should be in /run.
Are you saying that ntpd needs to be built (or run) with different parameters?
For me, /var/run is a symlink (/var/run -> /run), although I'm not sure why.
FHS lists /var/run
On 03/21/2012 09:33 AM, Nathan Coulson wrote:
> ntpd says it's pidfile is in /var/run, when it should be in /run.
>
/var/run is symlink to /run, so does it really matter?
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See t
On Wed, Mar 21, 2012 at 4:26 AM, Armin K. wrote:
> On 03/21/2012 09:33 AM, Nathan Coulson wrote:
>> ntpd says it's pidfile is in /var/run, when it should be in /run.
>>
>
> /var/run is symlink to /run, so does it really matter?
first, it is a configuration file we written ourselves, and using /ru
Nathan Coulson wrote:
> ntpd says it's pidfile is in /var/run, when it should be in /run.
Yes, we need to change that in the /etc/ntp.conf in the book.
Since we have a compatibility sysmink, it's really only needed when we
update the ntpd version. It does need updating to ntp-4.2.6p5 which was
On Mar 21, 2012, at 7:41 AM, Nathan Coulson wrote:
> On Wed, Mar 21, 2012 at 4:26 AM, Armin K. wrote:
>> On 03/21/2012 09:33 AM, Nathan Coulson wrote:
>>> ntpd says it's pidfile is in /var/run, when it should be in /run.
>>>
>>
>> /var/run is symlink to /run, so does it really matter?
>
> fir
Qrux wrote:
> On Mar 21, 2012, at 7:41 AM, Nathan Coulson wrote:
>
>> On Wed, Mar 21, 2012 at 4:26 AM, Armin K. wrote:
>>> On 03/21/2012 09:33 AM, Nathan Coulson wrote:
ntpd says it's pidfile is in /var/run, when it should be in /run.
>>> /var/run is symlink to /run, so does it really m
On Wed, Mar 21, 2012 at 01:33:31AM -0700, Nathan Coulson wrote:
> ntpd says it's pidfile is in /var/run, when it should be in /run.
>
Replying to this, because I think Nathan expressed interest in
avahi. In avahi, if you use --localstatedir=/var it will create
/var/run during a DESTDIR install.
Ken Moffat wrote:
> On Wed, Mar 21, 2012 at 01:33:31AM -0700, Nathan Coulson wrote:
>> ntpd says it's pidfile is in /var/run, when it should be in /run.
>>
> Replying to this, because I think Nathan expressed interest in
> avahi. In avahi, if you use --localstatedir=/var it will create
> /var/run
On Fri, Mar 23, 2012 at 7:03 PM, Bruce Dubbs wrote:
> Ken Moffat wrote:
>> On Wed, Mar 21, 2012 at 01:33:31AM -0700, Nathan Coulson wrote:
>>> ntpd says it's pidfile is in /var/run, when it should be in /run.
>>>
>> Replying to this, because I think Nathan expressed interest in
>> avahi. In avah
Nathan Coulson wrote:
> What I should actually do on my own build, is break the /var/run
> symlink, and have two folders. Then I can see what is actually going
> where.
That's your choice of course, but there are a couple of issues. We
guarantee that /run is available for other boot scripts
On 03/24/12 17:36, Bruce Dubbs wrote:
> Nathan Coulson wrote:
>
>> What I should actually do on my own build, is break the /var/run
>> symlink, and have two folders. Then I can see what is actually going
>> where.
>
> That's your choice of course, but there are a couple of issues. We
> guarantee
Lemon Lime wrote:
> On 03/24/12 17:36, Bruce Dubbs wrote:
>> Nathan Coulson wrote:
>>
>>> What I should actually do on my own build, is break the /var/run
>>> symlink, and have two folders. Then I can see what is actually going
>>> where.
>> That's your choice of course, but there are a couple of
13 matches
Mail list logo
