RE: cron 3.0.1-19 will not run shell scripts

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John S. > Sent: Monday, October 30, 2006 5:04 PM > To: cygwin@cygwin.com > Subject: cron 3.0.1-19 will not run shell scripts > > Greetings, > I hope this is an easy one. > > Problem: > cron w

RE: How to configure cron's mail?

> -Original Message- > Sent: Tuesday, September 26, 2006 11:50 PM > To: Cygwin Users > Subject: How to configure cron's mail? > > Hi, > > Can I configure where cron sends the mail to? It seems to be > "[EMAIL PROTECTED]", where user is the account cron is running > under, but I > would l

RE: How to run rxvt

> > Panos Katergiathis wrote: > > I have rxvt installed but there is no shortcut in order to run it, > > I wrote a batch file and made a shortcut to run it: > > C:\Documents and Settings\dpchrist\My Documents\home>type rxvt.bat > @echo off > rem $Id: rxvt.bat,v 1.1 2005/10/18 04:17

RE: cron - error starting a service

> > $ /usr/bin/cron_diagnose.sh: This also did not find any errors. The > displayed version of this is 1.10. The revision in the source is 1.3 > 2004/12/21 16:14:4. Whereas the previous "older" version I was trying > before displays 1.8. Is my /usr/bin/cron_diagnose.sh really the latest > version?

RE: cron - error starting a service

> > # Used cron_diagnose.sh 1.8 repeatedly until it no longer found any > problems. > Please try the version of cron_diagnose.sh in /usr/bin (that is, /usr/bin/cron_diagnose.sh). It is a later version than what you reported above. --- -- Unsubscribe info: http://cygwin.com/ml/#unsubscri

RE: problem starting crontab services

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pierre A. Humblet > Sent: Monday, September 11, 2006 9:55 AM > To: cygwin@cygwin.com > Cc: Jon Barber > Subject: Re: problem starting crontab services > > > > From: "Larry Hall (Cygwin)" > > To: cyg

RE: change in behavior of make from 3.80 to 3.81

> -Original Message- > > $ make -f mk > make: *** No rule to make target `c\:/hoffman/foo/foo.c', > needed by `foo'. Stop > > [EMAIL PROTECTED] ~/foo > $ ../make381/usr/bin/make.exe -f mk > make: *** No rule to make target `c\:/hoffman/foo/foo.c', > needed by `foo'. Stop > > > So

RE: New cygwin verson breaks emacs

> -Original Message- > Sent: Wednesday, July 26, 2006 6:25 AM > To: cygwin@cygwin.com > Subject: New cygwin verson breaks emacs > > This happened to a perfectly good pre-cygwin update emacs. > This also happened after a new rebuild of emacs with the new > cygwin system. > > ***MEMORY-ERR

RE: scp timeout on dual-core processor

> -Original Message- > > I have the same exact problem as Steve: > > "I have a (what appears to be) similar problem also with a dual core > > (Centrino Duo) machine. My problem manifests when I attempt > to paste in an > X window (i.e. click the middle mouse button). I immediately (1

RE: ssh password-less cmds to Windows 2003 don't return any output

> -Original Message- > From: John McNulty [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 21, 2006 12:48 PM > To: Harig, Mark > Subject: Re: ssh password-less cmds to Windows 2003 don't > return any output > > On 21/06/06, Harig, Mark <[EMAIL PROTECT

RE: ssh password-less cmds to Windows 2003 don't return any output

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John McNulty > Sent: Wednesday, June 21, 2006 7:07 AM > To: cygwin@cygwin.com > Subject: ssh password-less cmds to Windows 2003 don't return > any output > > Hello, > > I've been testing executing co

RE: sshd connection reset by peer problem

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of marct > Sent: Thursday, June 15, 2006 10:23 AM > To: cygwin@cygwin.com > Subject: Re: sshd connection reset by peer problem > > > Thanks for the pointer. I removed all of my keys from the > .ssh d

RE: vim 7 gives error when editing /etc/hosts

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Frank Fesevur > Sent: Tuesday, June 13, 2006 5:35 AM > To: cygwin@cygwin.com > Subject: vim 7 gives error when editing /etc/hosts > > Hi, > > When I try to edit /etc/hosts with vim7, it gives this err

RE: ssh with tunnel stacktrace on core duo

> -Original Message- > [mailto:[EMAIL PROTECTED] On Behalf Of Jürgen Schmitz > Sent: Wednesday, June 07, 2006 6:36 AM > To: cygwin@cygwin.com > > Hi! > > I'm using cygwin SSH for a long time now on a centrino notebook. Now I > have to switch over to a new core duo notebook with 2 GB ram.

RE: 1.5.19: Problem with ssh

> -Original Message- > From: Eric Surjawinata [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 24, 2006 4:33 PM > To: Harig, Mark > Subject: Re: 1.5.19: Problem with ssh > > Actually, you are correct. When I typed exit, I am back in the > original session. I gue

RE: 1.5.19: Problem with ssh

> -Original Message- > From: Eric Surjawinata [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 24, 2006 4:19 PM > To: Harig, Mark > Cc: cygwin@cygwin.com > Subject: Re: 1.5.19: Problem with ssh > > Hi, > sorry for the implicitness of the message: > 1. Y

RE: 1.5.19: Problem with ssh

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eric Surjawinata > Sent: Wednesday, May 24, 2006 3:50 PM > To: cygwin@cygwin.com > Subject: 1.5.19: Problem with ssh > > Hi, > > I have problems ssh-ing to a cygwin installed on Windows xp. I know > t

RE: 1.5.19: Problem with cron and microsoft devenv

> > The simple crontab below will show you what environment variables cron > knows about. > > * * * * * /usr/bin/env > Correction: that crontab entry should have read: * * * * * /usr/bin/env > /tmp/env.txt -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

RE: 1.5.19: Problem with cron and microsoft devenv

> > Another question I have is about cron and environment variables. When > I run a shell, even cmd /c, under cron the environment variable > APPDATA doesn't get set. This seems odd to me. I believe APPDATA > gets set from shell32 which should be loaded when cron runs 'cmd /c > somescript.bat'.

RE: openssh 4.3p2-3 - Timeouts on an Intel Centrino Duo machine

> -Original Message- > From: Simon McQueen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 23, 2006 1:02 PM > To: Harig, Mark > Cc: cygwin@cygwin.com > Subject: Re: openssh 4.3p2-3 - Timeouts on an Intel Centrino > Duo machine > > > If you're un

RE: openssh 4.3p2-3 - Timeouts on an Intel Centrino Duo machine

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Simon McQueen > Sent: Tuesday, May 23, 2006 10:29 AM > To: cygwin@cygwin.com > Subject: openssh 4.3p2-3 - Timeouts on an Intel Centrino Duo machine > > Hi all, > > I note this thread: > http://source

RE: cron issue

> I believe the problem was in the user accounts I have > setup on my windows box. I have both a domain > account \rdavies, and a machine > account \rdavies. I'll spare you the > reasons why. While I had stopped and deleted the > service cron with cygrunsrv, I had never tried to > install and s

RE: cron issue

> I believe the problem was in the user accounts I have > setup on my windows box. I have both a domain > account \rdavies, and a machine > account \rdavies. I'll spare you the > reasons why. While I had stopped and deleted the > service cron with cygrunsrv, I had never tried to > install and s

RE: cron issue

>>1. What command sequence did you use to start the >> cron service on your computer? (In general, what >> commands did you use to set up package X? Or, what >> commands did you run prior to encountering a problem?) >[RD] I went the minimal effort route and ran /usr/bin/cron-config. I th

RE: cron issue

1. What command sequence did you use to start the cron service on your computer? (In general, what commands did you use to set up package X? Or, what commands did you run prior to encountering a problem?) Here is what I am using to start my cron service. cygrunsrv --install cron

RE: cron issue

Some steps you could try: 1. Run 'cygcheck -l cron' to list the files included in the 'cron' package. (This is a general recommendation for any Cygwin package.) 2. Read the file /usr/share/doc/Cygwin/cron.README to get some Cygwin-specific instructions about 'cron', including the use

RE: rvxt-20050409-1 console problem [SUMMARY]

1. Thanks for taking on the 'rxvt' package. I look forward to the code changes that will make 'man' pages more readable. > >(3) (a) add a command line option to say "force hide console" and use that from scripts > 2. I do not have any need for the script usage that you described so I a

RE: rvxt-20050409-1 console problem

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sven Köhler Sent: Monday, May 15, 2006 12:46 PM To: cygwin@cygwin.com Subject: Re: rvxt-20050409-1 console problem > > You should see it, or perhaps your PC is too fast. > > But prior to the rxvt windows, an

RE: rvxt-20050409-1 console problem

Shouldn't the console-hiding code be unnecessary? Here is a simple approach that I have been using (and have written to this list previously) which makes it possible to start rxvt without resorting to starting a console first: 1. Using MS Windows Explorer, locate the 'rxvt' binary in your

RE: Win2003 server and cron/sshd as services (1.5.19)

Please see item 2 again. Do not include *ANY* quotes around -D when passed as an argument to '--args'. I am writing now to say that this behavior has been fixed. Since the last time I wrote, I have upgraded 'bash' to the latest version. I am guessing that this fixed the problem. $ cygcheck -c b

RE: make v3.80: *** [hello] Error 255

only add packages as you find that programs you need were not installed by default. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, May 08, 2006 5:48 PM To: Harig, Mark Subject: RE: make v3.80: *** [hello] Error 255 Mark,    Yeah,

RE: make v3.80: *** [hello] Error 255

The thread that starts here might be useful to you: "Make error 255 bug" http://www.cygwin.com/ml/cygwin/2003-09/msg01605.html Also, providing the output of 'cygcheck -s -v -r' as an attachment might reveal something that someone on this list could use to identify the source of the problem you'r

RE: Win2003 server and cron/sshd as services (1.5.19)

> > [EMAIL PROTECTED] ~ > $ cygrunsrv -I sshd --shutdown -p /usr/sbin/sshd -a "-D -ddd" \ >-d "CYGWIN sshd" -u sshd_server -w a_fine_password -e >"CYGWIN=binmode ntsec tty" 1. I assume that you meant to provide a "\" after '-e' in the second line of your command above, correct? 2. In

RE: Win2003 server and cron/sshd as services (1.5.19)

> > # If there is a running service, then stop it and remove it. > cygrunsrv --query sshd > /dev/null 2>&1 && { >cygrunsrv --stop $service; >cygrunsrv --remove $service; > }; Correction: '$service' should be replaced with 'sshd' in the two lines above. -- Unsubscribe info: ht

RE: Win2003 server and cron/sshd as services (1.5.19)

> I've been having problems getting cron/sshd to work properly (as > services or not as services) on a Win 2003 server. I understand that > certain attributes of the SYSTEM account changed in win2003, and I've > tried to allow ssh-host-config to setup sshd, but with no success. I > have tried se

RE: scp timeout on dual-core processor

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Baldwin Sent: Tuesday, May 02, 2006 4:27 AM To: cygwin@cygwin.com Subject: RE: scp timeout on dual-core processor (text deleted) >OK, now I don't believe my problems are related to the CPU(s). I disab

scp timeout on dual-core processor

The Cygwin version of the openssh utility program, 'scp', appears to have a defect that prevents it from copying files above a certain size, when 'scp' is running on computers with Intel dual-core processors. Here is the information that I have gathered so far: 1. ssh from the client machine (wh

RE: rxvt as Bash login console

> > > I was able to reduce my rxvt.bat file to this: > > [EMAIL PROTECTED]:~$ cat rxvt.bat > @echo off > rem $Id: rxvt.bat,v 1.1 2005/10/18 04:17:23 dpchrist Exp $ > C: > chdir C:\cygwin\bin > rxvt -fn "Lucida Console-11" -e /bin/bash --login -i > You should be able to

RE: cygcrypt-0.dll infected

> > It's amazing how many people use broken anti-virus software, > judging by > the number of times this was reported. The real solution is > to get the > anti-virus patterns fixed. One workaround that was suggested was to > recompile libcrypt, which removes the pattern (one can assume that th

RE: cygcrypt-0.dll false virus positive?

> -Original Message- > From: Walter Garcia-Fontes > Sent: Monday, January 10, 2005 10:44 AM > To: Cygwin > Subject: cygcrypt-0.dll false virus positive? > > > Since this morning I get Trend Micro Office Scan antivirus to report a > virus in /usr/bin/cygcrypt-0.dll. It is strange since th

RE: Is Cygwin cron supposed to send e-mail reports?

> > > ssmtp is less likely to suffer rebase issue. Use ssmtp-config. > > I don't seem to have it: > > [EMAIL PROTECTED]:~$ updatedb > [EMAIL PROTECTED]:~$ locate smtp-config > [EMAIL PROTECTED]:~$ smtp > smtpapi.dll smtpcons.mfl smtpctrs.dll smtpctrs.ini > smtpcons.dll

RE: Problems starting rxvt

> -Original Message- > From: Jesper Nygårds > Sent: Monday, December 13, 2004 2:10 AM > To: cygwin > Subject: Problems starting rxvt > > > I have some problems when trying to run rxvt on my newly > installed cygwin. > > I have edited the cygwin.bat script to read as follows: > > @echo

cron_diagnose.sh version 1.8

Attached below is version 1.8 of this diagnostic script. Thanks to Pierre A. Humblet for additional tests that check to see that the /etc/group and /etc/passwd files have valid entries for 'SYSTEM' and 'Administrators.' (Please send any replies to the mailing list, and NOT to me. Please do NOT i

RE: sshd in Windows 2003 server

> -Original Message- > From: daniel > Sent: Thursday, December 02, 2004 6:32 AM > To: [EMAIL PROTECTED] > Subject: sshd in Windows 2003 server > > > Hi, > I've installed sshd succesfully a couple of time on WinXP > machines > following the instructions at > http://pigtail.net/LRP

RE: Patch to /etc/profile to deal with $HOME with a space

> -Original Message- > From: Harig, Mark > Sent: Tuesday, November 30, 2004 2:26 PM > To: [EMAIL PROTECTED] > Subject: RE: Patch to /etc/profile to deal with $HOME with a space > > > > > > > > > 4. This problem could be reported to Bugzi

RE: Patch to /etc/profile to deal with $HOME with a space

> > > > 4. This problem could be reported to Bugzilla, with > >a patch file attachment. Please see > > > >http://sourceware.org/bugzilla/enter_bug.cgi?product=cygwin > > > >and select 'Cygwin Applications' as the Component. > > > >After you have entered the Summary and Descrip

RE: Patch to /etc/profile to deal with $HOME with a space

> > 4. This problem could be reported to Bugzilla, with >a patch file attachment. Please see > >http://sourceware.org/bugzilla/enter_bug.cgi?product=cygwin > >and select 'Cygwin Applications' as the Component. > >After you have entered the Summary and Description, revisit >

RE: Patch to /etc/profile to deal with $HOME with a space

1. Thank you for the patch file. 2. More fundamentally, this is a problem in /etc/defaults/etc/profile, instead of with /etc/profile. 3. This file belongs to the 'base-files' package: $ /usr/bin/cygcheck -f /etc/defaults/etc/profile base-files-3.1-4 4. This problem could be reported t

RE: Upgraded man command

> -Original Message- > From: Igor Pechtchanski > Sent: Wednesday, November 24, 2004 12:37 PM > Subject: RE: Upgraded man command > > Sure, but that'll only work if base-files is > reinstalled/upgraded at the > same time as the man package. If we want the man package to be > self-contai

RE: Upgraded man command

> From: Christopher Faylor > Sent: Wednesday, November 24, 2004 11:57 AM > Subject: Re: Upgraded man command > > This seems like a good candidate for bugzilla: > > http://sourceware.org/bugzilla/enter_bug.cgi?product=cygwin > > The component for the bug would be "Cygwin Applications". > > ---

RE: Upgraded man command

> > Possibly, the following code in /etc/postinstall/man.sh > should be changed: > >if [ ! -e ${datadir}/misc/man.conf ] ; then > cp ${datadir}/misc/man.conf.default ${datadir}/misc/man.conf > chmod 644 ${datadir}/misc/man.conf >fi > > to: > >if [ ! -e ${datadir}/misc/ma

RE: Upgraded man command

> -Original Message- > From: Igor Pechtchanski > Sent: Wednesday, November 24, 2004 11:32 AM > To: Andy Hall > Subject: RE: Upgraded man command > > Andy, > > Do you have both /etc/postinstall/man.sh and > /etc/postinstall/man.sh.done? > If so, then the newer version of the postinstall

RE: /etc/profile error

> > > >Look for a very current mirror and update. > > Sorry for the very ignorant question, but what is one supposed to do > with base-files-3.1-4.tar.bz2? Up to now I've been doing all > installations with the Cygwin installer app

RE: packages that should be in the cygwin distribution but aren't

> > > screen > > > > In some cases we have packages which offer > similar-but-not-identical behavior > > but in some cases (ping, screen) we don't have anything > close, AFAIK. > > I've been running screen on cygwin for years - originally using > http://dellelce.com/code/screen/ - though it wa

RE: Cygwin Cron - Cannot Switch user context

Please run this diagnostic script. It will attempt to locate many types of common problems with cron on cygwin. http://sources.redhat.com/ml/cygwin/2004-07/msg00207.html Please read the output of the script carefully. If it finds problems, it suggests possible fixes, and it will also recommend

RE: Cron malfunction after date change

> > >>cron.log, crontab.txt and cygcheck.txt attached. Stopping > and starting > >>cron is workaround that does resume correct cron behaviour, up until > >>next date change. I've been able to reproduce this > >>(http://cygwin.com/ml/cygwin/2004-11/msg00153.html) problem also on > >>WinXP with s

RE: Cron under Cygwin/Windows XP

> $ cron_diagnose.sh > cron_diagnose.sh 1.3 > Please run version 1.7 of this diagnostic script. It fixes some problems that were in the earlier versions, and detects some error conditions that the earlier versions did not. http://sources.redhat.com/ml/cygwin/2004-07/msg00207.html P.S., P

RE: Cron malfunction after date change

> > cron.log, crontab.txt and cygcheck.txt attached. Stopping > and starting > cron is workaround that does resume correct cron behaviour, up until > next date change. I've been able to reproduce this > (http://cygwin.com/ml/cygwin/2004-11/msg00153.html) problem also on > WinXP with slightly ol

RE: Cron malfunction after date change

Please run this diagnostic script. It will attempt to locate many types of common problems with cron on cygwin. http://sources.redhat.com/ml/cygwin/2004-07/msg00207.html Please read the output of the script carefully. If it finds problems, it suggests possible fixes, and it will also recommend

RE: Problem with installing crontab on Cygwin(1.5.11/1005.11.0.0)/WinXP SP2

> > > > This did it. Group 18 (SYSTEM) was not in /etc/group; instead, > > /etc/group only contained domain groups, not local groups. I ran > > 'mkgroup -l -d > /etc/group' to recreate the file. > > Glad it's fixed. > > Hey Mark, care to add another test to cron_diagnose? > (see sample in postin

RE: Problem with installing crontab on Cygwin(1.5.11/1005.11.0.0)/WinXP SP2

> > On Wed, 3 Nov 2004 09:24:37 -0500, Pierre A. Humblet > <[EMAIL PROTECTED]> wrote: > > > > crontab chowns the crontab file group to 18. Make sure that gid 18 > > is in /etc/group. Also I find it hard to believe that the strace you > > got gives no useful information. > > This did it. Group 1

RE: Problem with installing crontab on Cygwin(1.5.11/1005.11.0.0)/WinXP SP2

> > I'm getting the following error when trying to install a > crontab on my account: > > $ crontab -e > # editing my crontab here... > chown: Invalid argument > Please run this diagnostic script. It will attempt to locate many types of common problems with cron on cygwin. http://sources.red

RE: cron start error

Please do not include email addresses in replies. -- 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/

RE: ssh under windows 2003 server

> > > I appreciate the feedback, I tried the -r option but it does not work: > The sshd service does not start at all! > > openssh 3.8.1p1-1 > As was documented in the announcement for the latest release of openssh, the '-r' switch applies to that release. It does not apply to

RE: cron start error

> So I did the following: > 1. run cron_diagnose.sh (ver 1.6), which did not find any problems. Although it is unlikely to locate the source of your problem, please try running ver. 1.7: http://sources.redhat.com/ml/cygwin/2004-07/msg00207.html > b. output of 'cygcheck -srv' (Note: I got a > '

RE: cron and ssh with homeshare variable

> > My problem is that the system try to create a directory > '//ALISANDRE/homes/.ssh'. and '//ALISANDRE/homes/ this is > the value for > HOMESHARE , the system chearch to write in know_hosts file , > so i want > change this value by /home/gurkan definitively (even if a > reboot ) but i > can

RE: HOw to install emacs?

The Cygwin version of emacs is separate and distinct from the GNU version of emacs that (also) runs on Windows. The Cygwin version should, by default, be installed in your Cygwin path and can be started from a Cygwin shell prompt with the command "emacs". It will run in the Cygwin command window

cron_diagnose.sh version 1.7

> v1.6: permission fail for /etc/passwd: > for fname in /etc/passwd /etc/group; do >/usr/bin/ls -ld $fname | egrep -q '^-r..r..r.. '; >if [ $? -ne 0 ]; then > echo "The permissions on the file $fname are not correct." > echo "Please run 'chmod +r $fname', and run this script again

cron_diagnose.sh version 1.6

> > Sure enough, after creating the directory cron now works. > Neat script. > Thanks! (Shouldn't the installation have created the > directory, though?) > This diagnostic script came about because there are a number of environmental elements that have to be in place before cron can run. Al

RE: Problem running runmqsc from cron

> -Original Message- > From: Mike Kenny (email address deleted) > Sent: Friday, May 21, 2004 5:15 AM > To: cygwin > Subject: Problem running runmqsc from cron > > > I have written a number of scripts to monitor queue depth and > channel status on my MQ server. These work fine from the

RE: CRON problems

Please delete respondents' email addresses from any replies. Spammers harvest email addresses from mailing lists. > -Original Message- > From: Hank Statscewich > Sent: Thursday, May 06, 2004 7:13 PM > To: Harig, Mark > cc: [EMAIL PROTECTED] > Subject: RE: CRON p

RE: CRON problems

> > Two places to look for the actual error are /var/log/cron.log and the > Windows event log. Perhaps Mark can add this to the output of his > script... > Igor > -- I assume that what you are suggesting is that some text pointing the user to /var/log/cron.log be added, not actually displ

RE: CRON problems

> > Hmm, seems to me like checking ownership and permissions of cron.pid > would be something the cron_diagnose.sh should do. What happened was > that you ran it initially as your normal user account, and > the pid file > was created. Then when you tried to start it as a service, it was > runni

RE: 1.5.9: cron hangs on 2003 server

Please run the cron_diagnose.sh script to see if it can identify any problems with your cron set up and related files. The latest version of this script can be found at: http://sources.redhat.com/ml/cygwin/2004-03/msg00379.html Please read the output of this script carefully. You may need to ru

RE: CRON problems

Please run cron_diagnose.sh version 1.5. Numerous bugs have been found and fixed. This version can be found (as an attachment) on the mailing list at: http://sources.redhat.com/ml/cygwin/2004-03/msg00379.html > -Original Message- > From: Hank Statscewich > Sent: Wednesday, May 05, 2004 8

RE: Unable to get CRON to work

Please do not include email addresses in replies. My understanding is that it allows spammers to search mailing lists for valid email addresses. congratulations on getting cron to work. > Sent: Tuesday, April 27, 2004 8:25 AM > To: Harig, Mark; 'Sachar, Bradley (NIH/OD)' >

RE: Unable to get CRON to work

til you login after changing the files. > -Original Message- > Sent: Wednesday, April 21, 2004 2:56 PM > To: 'Sachar, Bradley (NIH/OD)' > Cc: Harig, Mark > Subject: RE: Unable to get CRON to work > > Hello, > > I permit to write you directly out

RE: Unable to get CRON to work

> -Original Message- > Sent: Monday, April 12, 2004 5:52 PM > To: '[EMAIL PROTECTED]' > Subject: Unable to get CRON to work > > > Cygwin Support, > > I have done a new installation of cygwin into the C:\cygwin > folder. CRON > does not seem to be waking up and executing the crontab.

RE: cron will not execute commands

nfig' to set up your ~/.ssh directory with the appropriate files. In short, it appears that cron is unrelated to the problems that you are seeing. > -Original Message- > From: steve > Sent: Monday, March 22, 2004 10:42 PM > To: Harig, Mark > Subject: RE: cron will not ex

RE: cron will not execute commands

1. Here is a more recent version of the diagnostic script. It has fixed several bugs. Please run it. http://cygwin.com/ml/cygwin/2004-03/msg00379.html 2. It's not clear from your message whether you are having problems getting cron to run, or whether you are having problems only wi

cron_diagnose.sh version 1.5

This version fixes several long-standing bugs. Thanks to Wayne Winch for pointing these out. -- cron_diagnose.sh will attempt to diagnose problems with cron. It will not modify any files on your computer. You might need to run the script several times. Each time that it finds

RE: cron problem report

> > % crontab -l > # DO NOT EDIT THIS FILE - edit the master and reinstall. > # (/tmp/crontab.3928 installed on Mon Mar 1 15:03:19 2004) > # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 > corinna Exp $) > * * * * * `date` >> ${HOME}/foo.log > % Do not include backquotes on 'date' -

RE: cron problem report

Please try version 1.4. It has additional checks. http://sources.redhat.com/ml/cygwin/2004-02/msg01341.html > -Original Message- > From: Seiji Tokunaga [mailto:[EMAIL PROTECTED] > Sent: Monday, March 01, 2004 3:27 PM > To: [EMAIL PROTECTED] > Subject: cron problem report > > > Hi, > >

cron_diagnose.sh version 1.4

> Perhaps cron_diagnose.sh can be updated to > incorporate this checkpoint, i.e., that passwd > and group in /etc are readable by everyone. Done. Thank you for the feed back. Please try the new version of this diagnostic script and confirm that it does not report an error when it should not and

RE: Cron Running As UID 400

Please read the message in the Cygwin mailing list at: http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html It will provide you with a script that will attempt to diagnose the problem that you are having with cron. > -Original Message- > From: Winch Jr., Wayne S [mailto:[EMAIL PROT

RE: Running cygwin cron under WinXP SP1

> > The only thing I hadn't done before was the mkpasswd -l -d > and mkgroup > -l -d on first run of the original install, so don't know if > that made a > difference, but its working now. It does make a difference, and this problem is detected by the diagnostic script. When the problem is

RE: Running cygwin cron under WinXP SP1

Please read the message in the Cygwin mailing list at: http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html It will provide you with a script that will attempt to diagnose the problem that you are having with cron. > -Original Message- > From: Russell Hind [mailto:[EMAIL PROTECTED]

RE: what's the best venue for help with the cygwinized emacs?

I am reasonably confident that this list is the appropriate mailing list for the cygwin version of emacs. The "help-emacs-windows" mailing list is for a "native" (to Windows) version of emacs that is built using Microsoft's compilers. > -Original Message- > From: Thomas L Roche > Sent: Fr

RE: error 1062 when starting distccd

Here is someone's solution that uses "cygrunsrv": http://lists.samba.org/archive/distcc/2004q1/001960.html > > You could try the following alternatives to > "cygrunsrv": > >Start distccd - > > /usr/bin/distccd --daemon --nice 4 --log-file > /var/log/distccd.log --pid-file /var/run/di

RE: error 1062 when starting distccd

You could try the following alternatives to "cygrunsrv": Start distccd - /usr/bin/distccd --daemon --nice 4 --log-file /var/log/distccd.log --pid-file /var/run/distccd.pid Stop distccd - if [ -f /var/run/distccd.pid ]; then kill -s SIGTERM $(cat /var/run/distccd.pid); fi You c

RE: cron + network share(w/ full access?)

Please try running this diagnostic script to see if it can help identify the cause of your problem: http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html > -Original Message- > From: Alan London [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 01, 2004 11:38 PM > To: [EMAIL PROTECT

cron_diagnose.sh version 1.3

The previous version referred to the file: /usr/doc/Cygwin/cron.README This has been changed to reflect the new directory structure for documentation: /usr/share/doc/Cygwin/cron.README --- cron_diagnose.sh will attempt to diagnose problems with cron. It will not modify any file

RE: Windows 2003 Server & Cygwin Cron

1. Permissions for /var/cron/tabs/ should be 640, as you have reported. 2. Ownership for this file should be user.SYSTEM, as you have reported. 3. Please try the diagnostic script attached to this message: http://sources.redhat.com/ml/cygwin/2003-11/msg01001.html > -Original Messag

RE: Problems with trivial makefile

> > [EMAIL PROTECTED] ~/test_make2/test2 ^^^ Is there a reason why you have not created your own account instead of 'Administrateur'? When you first set up Cygwin, it should display messages about running 'mkpasswd' and 'mkgroup'. Typically, you will run a command such as: $ m

RE: Problems with trivial makefile

> -Original Message- > From: Guillaume du Pontavice [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2003 6:19 PM > To: [EMAIL PROTECTED] > Subject: Problems with trivial makefile > > > hello, > > i am in trouble with a trivial makefile, using cygwin > 1.5.5-1 and make > 3.80-1

RE: Home key doesn't work with TERM=screen

> > If I ssh to cygwin with TERM=screen, pressing Home in bash results in > beep and a tilde printed. I've checked infocmp screen output, khome is > set to \E[1~, as in linux and cygwin terminfo entries. > You can take control of your keyboard settings by adding definitions to your ~/.inputrc:

RE: where is g77?

Using setup.exe, look in the Devel category. There is a "gcc-g77" package. In general, to find a file that setup.exe supports, use the Setup Package Search capability at http://cygwin.com/packages/. This can be found on the http://cygwin.com web page. > -Original Message- > From: Mic

RE: ssh hangs

> > Hi, > I just want to do the minimal amount of configuration to get > me going with > ssh. I know the server works because I've logged in from > other linux boxes. > > Any thoughts? 1. Consider deleting your ~/.ssh directory on your ssh client computer and running the 'ssh-user-co

cron_diagnose.sh version 1.2

cron_diagnose.sh will attempt to diagnose problems with cron. It will not modify any files on your computer. You might need to run the script several times. Each time that it finds a problem, it stops and displays a descriptive message. Please read the messages that the script generates, espec

RE: Chronic Cron - cyg.txt (0/1)

> > I'd created /etc/cron.d at some stage manually as a FILE . > > Have now deleted it and created it as a DIRECTORY. > > BINGO everything works > > (I don't know where that is on a stupidity scale, but maybe Mark could > add a test for this to his cron_diagnose.sh) > Thank you for the feedbac

  1   2   3   >