removal of diskcheckd.conf breaks mergemaster

[Wesley Morgan]

Subject says it all. /usr/src/etc/Makefile still refers to
diskcheckd.conf...

-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED] _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
  6bone: 3ffe:1ce3:7::b4ff:fe53:c297
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

diskcheckd.conf

[Andrew Bliznak]

After CURRENT update I see this in /var/log/messages:

Jun 12 18:50:48 pyvo diskcheckd[204]: open /etc/diskcheckd.conf failure:
No such file or directory

I saw this commit message:

 revision 1.267
 date: 2001/06/03 20:15:10;  author: phk;  state: Exp;  lines: +9 -1
 Add diskcheckd to /etc/rc with a knob in rc.conf.

 Make the default setting YES for now to get some experience with it.

 Note: If people starts seeing disk errors because of this then it
 should not be backed.
 

But where diskcheckd.conf ?

*   *   1   *

--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: diskcheckd.conf

[Poul-Henning Kamp]

In message [EMAIL PROTECTED], Andrew Bliz
nak writes:

After CURRENT update I see this in /var/log/messages:

Jun 12 18:50:48 pyvo diskcheckd[204]: open /etc/diskcheckd.conf failure:
No such file or directory

I saw this commit message:

 revision 1.267
 date: 2001/06/03 20:15:10;  author: phk;  state: Exp;  lines: +9 -1
 Add diskcheckd to /etc/rc with a knob in rc.conf.

 Make the default setting YES for now to get some experience with it.

 Note: If people starts seeing disk errors because of this then it
 should not be backed.
 

But where diskcheckd.conf ?

My bad, forgot to add diskcheckd.conf to src/etc/Makefile.

Done now.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message