Bug 69334 - Fix for /suphp.log (should be /var/log/suphp.log)
Summary: Fix for /suphp.log (should be /var/log/suphp.log)
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-20 09:50 UTC by Jeremy Chadwick
Modified: 2004-07-23 08:30 UTC (History)
0 users

See Also:

Attachments
file.diff (881 bytes, patch)
2004-07-20 09:50 UTC, Jeremy Chadwick 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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