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 To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Andrew DeFaria Newsgroups: gmane.os.cygwin Subject: Re: (Fwd) Cron oddity Date: Fri, 26 Jul 2002 13:40:36 -0700 Lines: 57 Message-ID: <3D41B3C4.8060102@Salira.com> References: <3D416CC4 DOT 3488 DOT 4B26A821 AT localhost> Reply-To: cygwin AT cygwin DOT com NNTP-Posting-Host: 206.184.204.2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1027716009 1130 206.184.204.2 (26 Jul 2002 20:40:09 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Fri, 26 Jul 2002 20:40:09 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en Paul Derbyshire wrote: > On 26 Jul 2002 at 11:36, Harig, Mark A. wrote: > >> 1. Consider installing 'mutt' using setup.exe. > > More installing...*sigh*...The big problem with Windows is that > everything is self contained so everything is multi-megabyte > bloatware. The big problem with unix is that nothing is self > contained so you have to install one thing, find it doesn't work, > install something else, install something else... :) Well people are directing you to install tools they are familar with in an attempt to help you with your problem. One can view the Unix way as "well at least you have a choice of what to install - you could install everything!". Also, often with Windows administration you'll find people doing the same thing and asking you to install WSH or the Resource Kit, etc. >> 3. If you don't receive mail within 5 minutes (more like 5 seconds), >> then you need to troubleshoot your ssmtp and mutt setups. Read >> /usr/doc/Cygwin/mutt*, /usr/doc/Cygwin/ssmtp* (for example, did you >> run /usr/bin/ssmtp-config?). Also, see the manual pages for mutt and >> ssmtp... > > I did not run /usr./bin/ssmtp-config. I don't recall the ssmtp man > page saying I should do so. I'm starting to think the documentation > for some components of Cygwin could be improved a touch. Try /usr/doc/*! Often there is stuff in there that explains stuff like setting up things. man is more how to use stuff. Anyway, one thought is that cron has a limited view of what it can see on the network. I've heard tell that it can see only global network mount points. What's a global network mount point as opposed to a non global one is beyond me. That question was never answered for me. For example, using UNC pathnames I could access places like my home directory (mounted to my H drive) through cron but now other network places using UNCs. I never figured out how to tell the difference. As was suggested, try simple commands first. Assuming you get those working try a script, located in the root directory of your C drive. Did it work? If so then try from your original location. Did that work? Is that original location a network drive or network place (UNC name?)? Report your results back here. > > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/