Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040818232050.033bfd68@pop.prospeed.net> X-Sender: Date: Wed, 18 Aug 2004 23:26:08 -0400 To: Andrew DeFaria , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: Cron problem/Documentation and Setup In-Reply-To: References: <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040817222639 DOT 029cb138 AT pop DOT prospeed DOT net> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040818224737 DOT 033c63d8 AT pop DOT prospeed DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:13 PM 8/18/2004, you wrote: >Larry Hall wrote: > >>At 10:44 PM 8/18/2004, you wrote: >> >>>So is P or /home off limits when it comes to cron? Why did this work at my last company? I think it's probably due to the "public" share point versus "non-public" share point (which I never totally understood before) and I'm fearing that I will not be able to convince the powers that be to change it! :-( >> >>Bingo! >> >>You can always resort to running cron as you instead of 'SYSTEM'. As long as you're the only user that needs to run under 'cron', that should work without changing the permissions of your network shares. > >I'd hate to have to resort to that! > >This doesn't explain why it worked at my last company and why I could have sworn it used to work here up until about a week ago. Well, if you can check the access permissions on the share in question, you should be able to determine whether this is an issue or not. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/