From owner-freebsd-questions  Thu Jan 29 15:17:46 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA15259
          for questions-outgoing; Thu, 29 Jan 1998 15:17:46 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gatekeeper.peerlogic.com (firewall-user@gatekeeper.peerlogic.com [204.31.26.2])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA15251
          for <freebsd-questions@FreeBSD.ORG>; Thu, 29 Jan 1998 15:17:43 -0800 (PST)
          (envelope-from jolp@peerlogic.com)
Received: by gatekeeper.peerlogic.com; id QAA24169; Thu, 29 Jan 1998 16:16:33 +0800
Received: from unknown(204.31.26.167) by gatekeeper.peerlogic.com via smap (3.2)
	id xma024166; Thu, 29 Jan 98 16:16:21 +0800
Received: from legacy ([204.31.26.190]) by internal-dns.peerlogic.com
          (Netscape Messaging Server 3.01)  with SMTP id AAA10490
          for <freebsd-questions@FreeBSD.ORG>;
          Thu, 29 Jan 1998 15:14:28 -0800
Message-Id: <3.0.5.32.19980129160900.008f4940@pop>
X-Sender: jolp@pop
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 29 Jan 1998 16:09:00 -0800
To: freebsd-questions@FreeBSD.ORG
From: "John Olp" <jolp@peerlogic.com>
Subject: Wu-Ftp umask problems
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions"

Hello.  I'm having great difficulty with using wu-ftp as presented in it's
accompanying documentation.  The problem is that the upload directive in
the ftpaccess file can allow or disallow (sub)directory creation if the
"dirs" or "nodirs" commands are pressent, but when it's allowed, the
directories that are created are not of the form <user> <group> <mode> as
is listed in the rest of the upload directive.  I know that the daemon is
processing the directive, because files that are uploaded are set
correctly.  It's just the directories that are misbehaving.

I tried setting the umask (-u) option on the command line in inetd.conf,
and can get it to create the directories with the proper permissions, but
the <owner> <group> id's are not set correctly.

Please help.

-John