From owner-freebsd-bugs  Thu Oct  2 06:20:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA25052
          for bugs-outgoing; Thu, 2 Oct 1997 06:20:05 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA25007;
          Thu, 2 Oct 1997 06:20:01 -0700 (PDT)
Resent-Date: Thu, 2 Oct 1997 06:20:01 -0700 (PDT)
Resent-Message-Id: <199710021320.GAA25007@hub.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, gfoster@gfoster.com
Received: from gfoster.intr.net (gfoster.intr.net [207.32.93.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA24623
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 2 Oct 1997 06:12:34 -0700 (PDT)
Received: (from gfoster@localhost)
	by gfoster.intr.net (8.8.7/8.8.6) id JAA01609;
	Thu, 2 Oct 1997 09:12:33 -0400 (EDT)
Message-Id: <199710021312.JAA01609@gfoster.intr.net>
Date: Thu, 2 Oct 1997 09:12:33 -0400 (EDT)
From: Glen Foster <gfoster@gfoster.com>
Reply-To: gfoster@gfoster.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: misc/4679: xtend(8) doesn't handle the "dump" command correctly
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         4679
>Category:       misc
>Synopsis:       xtend(8) doesn't handle the "dump" command correctly
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct  2 06:20:00 PDT 1997
>Last-Modified:
>Originator:     Glen Foster
>Organization:
self
>Release:        FreeBSD 2.2-STABLE i386
>Environment:

	affects only sites running the tw0 optional device driver and 
	xtend(8)/xten(1) software.

>Description:

	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.

>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.

>Fix:
	
	Apply the patch:

*** /usr/src/libexec/xtend/user.c.orig	Thu Oct  2 08:54:35 1997
--- /usr/src/libexec/xtend/user.c	Thu Oct  2 08:55:05 1997
***************
*** 73,78 ****
--- 73,79 ----
        }
      } else if(!strcmp("dump\n", cmd)) {
        strcpy(dumppath, X10DIR);
+       strcat(dumppath, "/");
        strcat(dumppath, X10DUMPNAME);
        if((dumpf = fopen(dumppath, "w")) != NULL) {
  	for(h = 0; h < 16; h++) {

>Audit-Trail:
>Unformatted: