Bug 4679 - xtend(8) doesn't handle the "dump" command correctly
Summary: xtend(8) doesn't handle the "dump" command correctly
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 2.2-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1997-10-02 14:20 UTC by Glen Foster
Modified: 1998-04-18 14:46 UTC (History)
0 users

See Also:

Attachments
file.diff (406 bytes, patch)
1997-10-02 14:20 UTC, Glen Foster 		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 Glen Foster 1997-10-02 14:20:00 UTC 
	The xtend man page describes a command "dump" to the xtend
	daemon.  As shipped, xtend tries to write the dump file to
	an inappropriate location, one where it has no write permission
	and is not logically tied to the program.

Fix: Apply the patch:
How-To-Repeat: 
	Compile a kernel with the tw0 device, set xtend_enable="YES" in 
	/etc/rc.conf.  Run "xten -" and issue the command "dump" to the
	xtend daemon.  Rather than writing a status.out file in 
	/var/spool/xten/, the command will generate an error.
Comment 1 stark freebsd_committer freebsd_triage 1998-04-18 14:43:45 UTC 
State Changed
From-To: open->closed

Suggested patch committed to -CURRENT and RELENG_2_2.