Bug 69334

Summary: Fix for /suphp.log (should be /var/log/suphp.log)
Product: Ports & Packages Reporter: Jeremy Chadwick <freebsd>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Jeremy Chadwick 2004-07-20 09:50:21 UTC 
	The present suphp port has some incorrect framework for specification
	of where the logfile points, assuming the user DOES NOT specify the
	LOG_PATH variable upon build (by default, it's empty).  The logfile
	will end up in / (a.k.a. /suphp.log), which is naughty.

	The included Makefile patch should fix things up by removing LOG_PATH
	and WITH_LOGNAME, and using a single variable: LOGFILE, which by
	default points to /var/log/suphp.log.

Fix: See attached patch below.

How-To-Repeat: 	Build suphp without defining LOG_PATH.
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2004-07-23 08:30:01 UTC 
State Changed
From-To: open->closed

committed, thanks