From 0 Mon Sep 17 00:00:00 2001

From: "Dmitry V. Levin" <ldv@altlinux.org>

Date: Mon, 15 Oct 2007 22:22:33 +0000

Subject: [PATCH 02] Apply dhcp-3.0.3-alt-defaults.patch

diff --git a/dhcp/server/dhcpd.conf.5 b/dhcp/server/dhcpd.conf.5

index defaced..defaced 100644

--- a/dhcp/server/dhcpd.conf.5

+++ b/dhcp/server/dhcpd.conf.5

@@ -2802,8 +2802,8 @@ The syntax of the \fIsyslog.conf\fR file may be different on some

 operating systems - consult the \fIsyslog.conf\fR manual page to be

 sure.  To get syslog to start logging to the new file, you must first

 create the file with correct ownership and permissions (usually, the

-same owner and permissions of your /var/log/messages or

-/usr/adm/messages file should be fine) and send a SIGHUP to syslogd.

+same owner and permissions of your /var/log/messages

+file should be fine) and send a SIGHUP to syslogd.

 Some systems support log rollover using a shell script or program

 called newsyslog or logrotate, and you may be able to configure this

 as well so that your log file doesn't grow uncontrollably.