Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: Cron problem/Documentation and Setup Date: Wed, 18 Aug 2004 20:13:31 -0700 Lines: 22 Message-ID: References: <6.1.0.6.0.20040817222639.029cb138@pop.prospeed.net> <6.1.0.6.0.20040818224737.033c63d8@pop.prospeed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 12.9.207.207 User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) In-Reply-To: <6.1.0.6.0.20040818224737.033c63d8@pop.prospeed.net> X-IsSubscribed: yes 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. -- Do illiterate people get the full effect of alphabet soup? -- 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/