Message-ID: <4734F35C.18E4808D@dessent.net>
Date: Fri, 09 Nov 2007 15:55:08 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Permissions/acl problem
References: <fh114b$d0u$1@ger.gmane.org> <47349DE5.6020500@cygwin.com> <fh2psn$qg8$1@ger.gmane.org> <4734EDA4.FAE2802E@dessent.net> <4734F100.30108@cygwin.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

"Larry Hall (Cygwin)" wrote:

> the info already provided.  But given that the OP was able to list the
> contents of the share from cron, he's managed this in some way.  Assuming
> this information is not faulty, 'smbntsec' may indeed be what he needs to
> manipulate permissions on these files.  But I would certainly encourage the
> OP to review the current state of his configuration given the information
> above and make sure that he's clear on what's required to accomplish the
> desired end.

If it was a smbntsec problem, he would have had problems in both a
normal user shell and from within the cronjob.  But it worked fine from
his normal account (without smbntsec set) and was read-only from within
the cronjob, which to me implied that it was being accessed in the
context of the guest account, i.e. it was still readable as guest but
required authentication to write.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/