From owner-freebsd-questions Fri Nov 12 10:11:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from broccoli.graphics.cornell.edu (broccoli.graphics.cornell.edu [128.84.247.53]) by hub.freebsd.org (Postfix) with ESMTP id 17D7D14BC8 for ; Fri, 12 Nov 1999 10:11:04 -0800 (PST) (envelope-from mkc@Graphics.Cornell.EDU) Received: from graphics.cornell.edu by broccoli.graphics.cornell.edu with ESMTP (1.37.109.16/16.2) id AA008770258; Fri, 12 Nov 1999 13:10:58 -0500 Message-Id: <199911121810.AA008770258@broccoli.graphics.cornell.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Lemle Geza Cc: freebsd-questions@FreeBSD.ORG Subject: Re: proftpd and authentication failure In-Reply-To: Your message of "Fri, 12 Nov 1999 08:57:11 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 13:10:57 -0500 From: Mitch Collinsworth Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >when I make a virtual server with its own password database and >directory, the user (which is only in this database, but not a UNIX user) >can log in, but can not write, unless 777 permission is granted on the >directory. My question: is there any way to have some more restrictive >permisions on the directory? Well I'm not using proftpd in this manner so I haven't had to figure this one out (yet). But I will suggest that you will probably find answers to detailed proftpd questions more quickly by consulting: - the proftpd web site: http://www.proftpd.org - the proftpd mailing list: (see the web site for details) - the proftpd faq: http://hamster.wibble.org/proftpd/proftpdfaq-8.htm l -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message