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 will not run any shell scripts. Description: As far as I can tell cron works fine, but cron will not run any shell scripts. The shell scripts work fine if invoked from the shell. The Cygwin distribution of 'cron' includes a shell script named 'cron_diagnose.sh' that you might find useful in locating the source of your problem. Run the following commands at your shell prompt: $ cygcheck -c cron $ cygcheck -l cron The first command will verify that your 'cron' installation is valid, or not. The second command will list the files included in the 'cron' distribution. You can use this list to locate 'cron_diagnose.sh' in your environment. --- -- 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: 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 like it to go to [EMAIL PROTECTED]. cygcheck -l cron cygcheck -l ssmtp See then the Cygwin-specific README files in /usr/share/doc/Cygwin/. --- -- 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: 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? The version number reported by the script is different from the version reported by CVS because several versions were released before the Cygwin project accepted the script. If you want to find out whether the script is the one installed with your installation of 'cron', you can uninstall 'cron' via setup.exe, and then re-install it. The script is no longer independent of the 'cron' package, but is included with it. -- 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: 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\hometype 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 It is not necessary to create a batch file. Simply right-click on the 'rxvt' binary in Windows Explorer, and then select 'Create Shortcut'. Once you have created a shortcut to 'rxvt', you can then right-click on it, select 'Properties' from the menu, and enter the above information from the batch file into the 'Target' field. Note that you can only do this for the shortcut -- you cannot modify the 'Target' field of the 'rxvt' binary. The shortcut may then be dragged and dropped to your Quick Launch toolbar, your desktop, etc. Also, you may create a '.Xdefaults' text file in your home directory. The Cygwin 'rxvt' will read this initialization file, just as it would in UNIX/Linux. It can be used to set long font names, geometry, colors, etc. See the 'rxvt' manual page for details. See also /usr/share/doc/Cygwin/rxvt-20050409.README, or whatever the appropriate README number is reported by 'cycheck -l rxvt'. -- 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: 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/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
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: cygwin Sent: Friday, September 08, 2006 10:27 PM Subject: Re: problem starting crontab services On 09/08/2006, Jon Barber wrote: hello cygwin gurus i can't get crontab services to start. i just followed the instruction from running cron_diagnose.sh version 1.5, and there were a number of things it reported wrong that i tried to fix. the final problem is when i try to start cron, i get the following error: ... Let me point out again that cron_diagnose does not handle W2K3 at all and that cron-config should be used instead. Much of the cron related traffic to this list is due to misguided attempts to use cron_diagnose. Pierre Also, do not download cron_diagnose.sh separately. It is included in the cygwin distribution of 'cron' (/usr/bin/cron_diagnose.sh). Version 1.5 of the script is out of date. -- 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: 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, I am guessing there is no way to write a makefile that will use make 3.81 that will work with Microsoft's cl. Is that correct? Or am I missing something? I can change cmake to put anything I want in the generated makefiles, but it will have to be something that is valid for cl. Suggestion: 1. $ mount -m $ mount -s -b --change-cygdrive-prefix / $ mount -m 2. Edit your 'mk' file to change c\:/hoffman to /c/hoffman. In general, change the drive: strings to /drive/ strings, after you have changed your cygdrive prefix. --- -- 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: 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-ERROR***: emacs[3060]: GSlice: failed to allocate 504 bytes (alignment: 512): Function not implemented My cygwin information is given as: CYGWIN_NT-5.1 1.5.21(0.156/4/2) 2006-07-23 20:11 Any other people out there with emacs problems GNU Emacs 22.0.50.1 $ cygcheck -c emacs Cygwin Package Information Package VersionStatus emacs21.2-13OK The above version has been available for quite some time and performs many editing functions without any run-time errors or crashes. Thanks for any feedback or advice You could try installing the currently-supported (and pre-built) version to see whether it would meet your editing needs until the next version of Emacs is announced as supported in the cygwin distribution. If you require some editing capability that only Emacs 22 provides, then you'll likely need to provide: - A (sufficiently) detailed description of the steps that you took to build Emacs from the source code - A detailed description of the run-time/editing steps that you performed that resulted in the problem that you are seeing --- -- 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: 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 (100% reproducible) get Disconnecting: Timeout, server not responding., and my ssh session dies. I just got a new machine with a centrino duo, dual core processor... Just another data point.. If there is anything I can do in terms of diagnosis please let me know. Thx, --Kurt If you are having this problem on a Dell laptop, then, as Larry Hall pointed out earlier, a software package from Embassy has been causing problems. As far as I know this was first described here: http://sourceware.org/ml/cygwin/2006-05/msg00790.html You should be able to contact either Dell or Embassy for a patch that fixes this problem. I have applied the fix on several dual-core Dell laptops and have not seen the 'scp-timeout' problem since. --- -- 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 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 command via password-less SSH (public key) logins from MacOSX and OpenVMS clients to a Redhat EL AS 4 server, and a WinXP Home system (with Cygwin's OpenSSH). All works ok and I can issue test commands like: $ ssh [EMAIL PROTECTED] ipconfig and see the output from ipconfig on the client. However I've just installed and configured Cygwin OpenSSH on a Windows 2003 server, and setup password-less logins (via public keys) as before. But when I try and issue a command via ssh from the client I get no command output back at all. The remote command just completes silently. The password-less login is working just fine. Does anyone else see this and have any idea why I'm getting this behavior? I do not see this and I do not know why you are seeing that behavior. I am reporting that $ ssh [EMAIL PROTECTED] server] [command] produces user-visible output when I run that command from RHEL 3 or RH 7.3. -- 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 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 PROTECTED] wrote: I do not see this and I do not know why you are seeing that behavior. I am reporting that $ ssh [EMAIL PROTECTED] server] [command] produces user-visible output when I run that command from RHEL 3 or RH 7.3. I just tried it from one of the RHEL AS 4 (update 3) systems. Same thing. So that's 3 different clients now and 3 different operating systems. The common denominator is the W2003 server. My guess is the one that was listed in one of the earlier replies, namely, to confirm that you have created the required special accounts required for running a Cygwin ssh service on Windows 2K+. Normally, 'ssh-host-config' will have done this for you, or will have prompted you for permission to do it. Consider posting your /etc/passwd, /etc/group, and /etc/sshd_config files (as attachments) to the Cygwin mailing list. Someone may see a problem with your configuration. For what it's worth, I used your test program, 'ipconfig', to check the cygwin sshd behavior on three W2003 servers. All three worked as expected, with the output of ipconfig displayed in my rxvt terminal window. Also, I am assuming that you are able to start an ssh client on your RHEL server and successfully connect to your W2003 server, and can run the 'ipconfig' command with the expected results when run interactively. -- 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: 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 directory and then ran ssh-keygen.exe which created 3 new sets of keys but I still get connection reset by peer: $ ssh -vvv localhost Unless you have an ssh server running on 'localhost', then this command will not work because your 'ssh' client has no server to communicate with. Setting up a (Cygwin) ssh service on your Windows computer is possible, but it's not likely that you want to do that because you have said that you are new to using ssh. Instead, you should find out the IP address of the ssh server, if any, is available on your network. Once you've found out that IP address, then you should first ping it to confirm that your computer has some basic network connectivity to that address. Cygwin provides a simplified method for creating ssh encryption- key files: ssh-user-config. After removing your present key files, run that script, and respond to its prompts. Typically, you will not need the RSA1 and DSA key types, so you can respond no when prompted to create them (they are less secure than the RSA2 key type). --- -- 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: 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 error: E303: Unable to open swap file for hosts, recovery impossible The file can be edited, but this never happened with 6.4 Regards, Frank vim appears to be unable to follow some links. The following steps lead to the above error for me, also. $ touch c:\foo.txt $ ln -s c:\foo.txt bar.txt $ vim bar.txt # vim reports the swap-file error On my computer, and I suspect on yours, /etc/hosts is a symbolic link to Windows 'hosts' file: $ ls -ln /etc/hosts lrwxrwxrwx 1 13558 545 37 Apr 4 18:11 /etc/hosts - C:\WINDOWS\system32\drivers\etc\hosts Curiously, the link does not cause an error if it was created using cygwin syntax: $ ln -fs /c/foo.txt bar.txt # assumes that you've set the cygdrive prefix to / $ vim bar.txt # No swap-file error is reported. Until the problem code and its solution can be identified, you should be able to use this workaround. --- -- 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 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. Any help is welcome, A number of users have reported what appear to be related symptoms of this problem, that is, Cygwin's ssh failing on computers (laptops only?) with dual-core CPUs. (Although I have seen this problem on three (identical) dual-core laptops, I no longer have access to those computers so I cannot investigate this problem any further.) If you are interested in helping to resolve this problem, you might try the following: 1. Use 'scp' to attempt to copy a file from your ssh server to your computer that has Cygwin installed on it. The file should be relatively large (greater than 100 kilobytes). If the problem is consistent, then you should see that scp fails to copy this large file (or try a set of large files). 2. Retry the scp command but use 'strace' to get some idea about where the code is failing. 3. Retry the command, but use 'gdb' to debug ssh or scp code. --- -- 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: 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 this is an old issue, however I scoured all the past issues with this and have not found a solution that worked for me (short of finding an older cygwin release and re-installing). Basically I installed Cygwin 1.5.19 and done all of the followings: install ssh, privilege separation=no, CYGWIN= ntsec tty content of: ... ran mkpasswd -l It's not clear from the above -- did you redirect the output of 'mkpasswd -l' to /etc/passwd? That is, $ mkpasswd -l /etc/passwd ... ran mkpasswd -d -u esurjawinata (for the users I want to use to ssh) Again, did you redirect this to /etc/passwd? $ mkpasswd -d -u esurjawinata /etc/passwd ... Output from ssh -v $ ssh -v [EMAIL PROTECTED] debug1: Next authentication method: password [EMAIL PROTECTED]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: Wed May 24 11:02:26 2006 from lt-esurjawinata Nothing works! Have I missed anything simple? What failed? From the above, it appears that you were able to log on. --- -- 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: 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. Yes, I redirected all output to the approp passwd and group file 2. The end of the verbose session throws me back to the bash prompt. no error message that I can detect Your log said: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last lo gin: Wed May 24 11:02:26 2006 from lt-esurjawinata What were you expecting different? You logged on to your computer, lt-esurjawinata, via ssh. ... throws me back to the bash prompt. Correct. So long as you realize that you are now one ssh level removed from your original login. --- -- 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: 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 guess the login process was so silent, that I didn't even realize that I finally have the correct configuration. The 'Last login: ...' message is the notice that you will see that should let you know that you have logged on to the ssh server, wherever that may be. You will see that message whether you specify '-v' to ssh or not. --- -- 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: 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://sourceware.org/ml/cygwin/2006-05/msg7.html I've just got a Dell Latitude D620 with a dual core processor and it's exhibiting what I think might be the same problem. In my case the issue appears when I'm checking out from CVS using ssh. Checkouts from repositories not using ssh work fine as do checkouts using ssh from my desktop (not dual core) using the same version of cygwin. I was also seeing the problem originally from CVS checkouts over ssh. I reduced the problem to 'scp' to simplify the diagnosis (i.e., the problem isn't with CVS, but with ssh/scp -- or something more fundamental). I do not have any helpful advice to offer on how to fix this problem, and, unfortunately, I no longer have access to the three (identical Dell M70) laptops that were having the problem. If you're unable to build and debug the openssh/cygwin code, then you may need to resort to installing TortoiseCVS, http://www.tortoisecvs.org/, which doesn't appear to have this problem on the dual-core Dell laptops. --- -- 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: 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 unable to build and debug the openssh/cygwin code,
then you may need to resort to installing TortoiseCVS,
http://www.tortoisecvs.org/, which doesn't appear to have
this problem on the dual-core Dell laptops.
I'm building the source as per:
http://cygwin.com/faq/faq-nochunks.html#faq.programming.buildi
ng-cygwin
... right now although I haven't quite worked out what on earth I'm
going to do with it once it's built. Thanks again for taking
the time to
reply.
Try debugging using gdb?
Working backwards (top down?), the error message that scp
issues is 'Timeout, server not responding.'. A search of the
Openssh source code shows that this is only issued by the function
'server_alive_check()' in the file clientloop.c. That function, in
turn is called by the function 'client_wait_until_can_do_something()',
in the same source file. 'server_alive_check()' is called if the
following condition fails:
ret = select((*maxfdp)+1, *readsetp, *writesetp, NULL, tvp);
if (ret 0) {
...
} else if (ret == 0)
server_alive_check();
My guess is that the call to select() needs to be checked to make
sure that it is being passed valid values. If it is, then the
code that provides select() (cygwin1.dll?) would need to be built
and linked to ssh/scp in order to find out whether the problem
lies deeper within the code (by using gdb to step into the call
to select()). If select() is *not* being passed valid values, then
backtracking would be necessary.
---
--
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: 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'. The simple crontab below will show you what environment variables cron knows about. * * * * * /usr/bin/env Also, 'man 5 crontab' describes cron's handling of environment variables. --- -- 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: 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: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
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 domain name\rdavies, and a machine account machine name\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 start the service using the 2 steps. When I tried, the -u rdavies flag actually picked up the machine not domain user. And it wouldn't start. I deleted the machine user (assigned to group none, and not likely to get any use anyway) and then reconfigured with cron-configure. Poof! I now have a new line every minute in the goofy log file I was testing with. Thanks for your help. If you are able to think of a test that can be added to cron_diagnose.sh, please post it on this mail list. It sounds like there should be a test to see whether the user's ID is valid for cron, by some definition. --- -- 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: cron issue
I believe the problem was in the user accounts I have setup on my windows box. I have both a domain account domain name\rdavies, and a machine account machine name\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 start the service using the 2 steps. When I tried, the -u rdavies flag actually picked up the machine not domain user. And it wouldn't start. I deleted the machine user (assigned to group none, and not likely to get any use anyway) and then reconfigured with cron-configure. Poof! I now have a new line every minute in the goofy log file I was testing with. Thanks for your help. If you are able to think of a test that can be added to cron_diagnose.sh, please post it on this mail list. It sounds as though there should be a test to see whether the user's ID is valid, by some definition. --- -- 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: 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 am neutral with respect to whether you add this new feature. If you decide to add the feature, I would suggest that you implement the usual three ways of using it: - highest priority: a command-line switch - next priority: an environment variable - lowest priority: the ~/.rxvt configuration file 3. FWIW, here is a font that I found useful. It has worked on various Windows versions (nt/2k/2003/xp) without any additional steps required on my part (i.e., no additional fonts needed to be installed). It is not mentioned in /usr/share/doc/Cygwin/rxvt-20050409.README. If you find it useful, please feel free to add it to the ones listed in that README file. Simply cutpaste the line to your ~/.Xdefaults. It resizes fairly well with Shift-[num +]/Shift-[num -]. rxvt*font: -outline-Courier New-normal-r-normal-normal-20-96-120-120-c-100-iso8859-1 --- -- 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: 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 of 'ssmtp' as a replacement for 'sendmail'. 3. Run '/usr/bin/cron_diagnose.sh' to see whether it can identify any problems with your cron setup. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nelson Pereira Sent: Tuesday, May 16, 2006 11:36 AM To: cygwin@cygwin.com Subject: RE: cron issue You had to install Sendmail to do this right? How did you do that? Did you follow a howto article or dsomething? I need to install sendmail also but from what I have read, sendmail doesn't work on cygwin... I get this: The owner and the Administrators need to have ..x permission to /usr/sbin/sendmail. Here are the current permissions: ls: /usr/sbin/sendmail: No such file or directory Any help you can provide to help me install sendmail would be greatly appreciated Regards, NPEreira I've configured cron using cron-config running as a service with the SERVICE account and as a service with myself. Initially, I created a crontab to run an rsync backup, which never initiated. I then opted for something simple and obvious, sending the date to a file. I've attached my log, crontab and the cygcheck. I've verified that the service is running (under XP) and that cron is running. Roger Davies PeopleSoft HRMS 970.506.7750 Important Notice: The contents of this electronic message and any attachments are intended only for the addressee and may contain confidential and privileged information. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail immediately and destroy all copies of the message and any attachments. Thank you. -- 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/ -- 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: 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 --shutdown \ --path /usr/sbin/cron --args -D \ --disp Cygwin cron --desc Cygwin vixie-cron service \ --user sshd_server --passwd your-fine-password; I am running Cygwin on Windows 2003, so the 'sshd_user'/'password' is required for my computer. I think that this is *not* required for Windows XP. In fact, you may not have set up an ssh service yet. I opted for exim instead of ssmtp, which I presume is OK. 2. To quote the README: Important: Make sure you have a Cygwin MTA (e. g. either exim or ssmtp) installed and configured! Cron tries to access the MTA by calling /usr/bin/sendmail. On Cygwin this is usually a symlink pointing to the appropriate binary. This symlink gets created by the MTA's configuration scripts (e. g. /usr/bin/exim-config or /usr/bin/ssmtp-config). The README has a typo, above. /usr/bin/sendmail should read /usr/sbin/sendmail. Confirm that /usr/sbin/sendmail is a symbolic link that points to your Cygwin MTA. --- -- 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: 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 think this is the recommended method for people who are setting up the cron service for the first time. I don't have a command line explicitly. What DOES happen at the minimum is that cygrunsrv installs a service called cron running as the user rdavies (me) using ntsec. I can confirm that the service is running, and that ps -ef reports that cron is active and running as the rdavies user. Have you tried running the commands recommended by cron_diagnose.sh for shutting down/uninstalling/installing/restarting the cron service, i.e., the following? C_dIf you are still unable to get cron to work, then try shutting C_ddown the cron service, uninstalling it, reinstalling it, and C_drestarting it. C_d C_dThe following commands will do that: C_d $ cygrunsrv --stop cron C_d $ cygrunsrv --remove cron C_d $ cygrunsrv --install cron -p /usr/sbin/cron -a -D C_d (You can also add a -u switch) C_d $ cygrunsrv --start cron C_d C_dIf the cron service does not start, try deleting the file C_d/var/run/cron.pid and then repeating the commands above. C_d C_dAlso, examine the log file for cron, /var/log/cron.log, C_dfor information that it might give you about the problem cron C_dis having. [RD] Symbolic link to exim: lrwxrwxrwx 1 rdavies mkgroup-l-d 13 May 15 16:46 /usr/sbin/sendmail - /usr/bin/exim Group--- ^^^ I am not sure whether the fact that you have not set a group value for your user account has any effect on your ability to run a cron service. I do not think that it does. --- -- 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: 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 Cygwin directory tree, for example, at c:\cygwin\bin. 2. Right-click on the 'rxvt.exe' icon and select 'Create Shortcut' from the menu. 3. Right-click on the 'Shortcut to rxvt.exe' icon and select 'Properties' from the menu. 4. In the 'Target' field, type the options that you want to specify for 'rxvt' during startup. For example, C:\cygwin\bin\rxvt.exe -e /bin/bash --login -i tells rxvt to run 'bash' as the shell, and tells bash to run as a login shell. 5. If desired, dragdrop the shortcut icon to your taskbar. Click on the icon to start 'rxvt' without using a console. Am I missing something, or is there still another reason to include the console-hiding code? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Peshansky Sent: Monday, May 15, 2006 10:47 AM To: cygwin@cygwin.com Subject: rvxt-20050409-1 console problem Hi, After installing rxvt-20050409-1, starting rxvt from a console bash hides that console. To reproduce: start a console bash, type rxvt or rxvt (either way), observe that the bash window goes away (the process is still running, though). I don't think the cygcheck output is relevant, since this looks like an rxvt problem (caused by the new code to hide the console). Chuck, if you can't reproduce this, please let me know and I'll provide more details. Igor -- -- 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: 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, another windows opens that gets closed immediatly. That's a console-window like the ones you see, when you run cmd.exe So the console-hiding code is the code, that causes, that the console-window disappears and that inly the rxvt-window remains. When I start rxvt via the shortcut icon, I see the same behavior regardless of whether I use version 2.7.10-6 or the latest version. So, whatever is happening in the background (console-closing or not) doesn't matter when starting rxvt via the shortcut. The issue, as I understand it, is that some users were starting 'rxvt' from a Cygwin console window (which, in turn, was started via a batch script) by using the command 'run rxvt'. In rxvt 2.7.10-6 and earlier versions, this command sequence would leave the console window displayed. The new console-hiding code causes the console window to be automatically hidden. If the shortcut icon approach to starting rxvt is used, then there is no need (that I know of) to have the console-hiding code included in 'rxvt' because no console would be displayed (or if it is, then it is already automatically hidden). This would then leave the console displayed for those users who need it. --- -- 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: 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 my earlier code, I had provided the following option to the cygrunsrv program: --args -D Note the double quotes around the '-D', above. I never would have suspected it, but those double quotes -- when used to install the cron service -- will cause cygrunsrv to fail when attempting to start cron. This surprised me because I use the double quotes around '-D' when starting sshd. In the case of starting 'sshd' the double quotes do not cause any problem. Going forward, for consistency, I have no quotes around '-D' for either 'cron' or 'sshd'. Can anyone else on the Cygwin mailing list test this behavior? Here are the prerequisites: Windows 2003 and an 'sshd_server' user account in your /etc/passwd (usually created by the script named 'ssh-host-config'), with a corresponding password for that special user account. The following command consistently fails: cygrunsrv --install cron --path /usr/sbin/cron --shutdown --args -D \ --disp Cygwin cron --desc Cygwin vixie-cron service \ --user sshd_server --passwd your-fine-password; The following command consistently works: cygrunsrv --install cron --path /usr/sbin/cron --shutdown --args -D \ --disp Cygwin cron --desc Cygwin vixie-cron service \ --user sshd_server --passwd your-fine-password; 3. If you are still not getting cron to start, then I would suspect that the password you are entering for the special account 'sshd_server' is incorrect. Here are some steps you could try to confirm the password: a. Log off your Windows account b. At the Windows login dialog, enter 'sshd_server' in the 'User name' field. c. Enter the password for this account (do NOT press [Enter] or click on 'OK'). d. In the 'Log on to' field, select the 'hostname' (this computer) value so that you are NOT logging on to your local network, if any). e. Click on 'OK' or press [Enter]. If the error message: The system could not log you on. Make sure your User name and domain are correct, then type your password again is displayed, then either you typed the wrong password or your knowledge of the password is incorrect. If the error message: The local policy of this system does not permit you to logon interactively is displayed, then your knowledge of the 'sshd_server' user account's password is correct. -- 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: 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're having. Please see also: http://cygwin.com/problems.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harold Rabbie Sent: Monday, May 08, 2006 3:39 PM To: cygwin@cygwin.com Subject: make v3.80: *** [hello] Error 255 This is the dumbest thing. The makefile couldn't be simpler: $ cat makefile hello: hello.c gcc -o hello hello.c When I run this, I get: $ make gcc -o hello hello.c make: *** [hello] Error 255 -- 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: make v3.80: *** [hello] Error 255
Please send all replies to the cygwin mailing list. This will increase your chances of getting a reply and the correct diagnosis of your problem. From your text below, it looks as though your Cygwin environment has several problems. 1. The PATH environment variable does not appear to have any reference to cygwin directories (c:\cygwin\bin, for example). It's surprising to me that you're able to get much to run. 2. cygcheck was not able to find 'id' (typically, this is C:\cygwin\bin\id.exe). This could be because you don't have the 'coreutils package installed, or because PATH does not reference any cygwin directories. 3. You might consider un-installing cygwin and carefully re-installing it. If you take this approach, then try installing cygwin in (at least) two stages. The first stage simply accepts the default packages that 'setup.exe' selects. Install these packages to completion and then start 'setup.exe' again. During the second stage, select the minimal set of additional packages that you want (for example, 'vim' or 'emacs', 'gcc', etc.). Then 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, I read that thread, and it refers to a problem with very long command lines. I don't think gcc -o hello hello.c qualifies. cygcheck says: $ cygcheck -s -v -r Cygwin Win95/NT Configuration Diagnostics Current System Time: Mon May 08 14:39:55 2006 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: \usr\vast\comet5\gcc\bin \windows\system32 . `id' program not found Does that help? Thanks! Harold -- 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: 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 disabled the 2nd core in the BIOS and I was still getting the problem. I think it is more likely to be some nasty interaction with some piece of software on this new machine. Please ignore my previous post (at least until I do a bit more investigation). Steve Following your message, I tried this also. I disabled two performance settings in the BIOS: one setting disabled the dual-core and the other setting disabled a feature that Intel is calling 'SpeedStep'. Even with both features disabled, the 'scp' commands listed in previous email messages failed. -- 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/ -- 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: 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 setting up both sshd and cron manually (following relevant
win2003 advice from
http://www.cygwin.com/ml/cygwin/2003-11/msg00368.html), but I still
cannot seem to get either service to work properly.
Have you stopped and started the ssh service several times? If so,
have you remembered to provide the password that that 'ssh-host-config'
requires you to create? It would be helpful in diagnosing your problem
if you were to provide the text of your commands for starting and
stopping
the ssh service.
Here is an edited copy of the command that I have put into a wrapper
script to start the ssh service. I am running sshd on several computers
running W2003. I have edited out the password that I use. See the
cygrunsrv documentation for a description of its options.
start_sshd.sh
#!/bin/bash
# Stop if any errors occur.
set -o errexit;
# If there is a running service, then stop it and remove it.
cygrunsrv --query sshd /dev/null 21 {
cygrunsrv --stop $service;
cygrunsrv --remove $service;
};
# Install the sshd service.
cygrunsrv --install sshd --shutdown --path /usr/sbin/sshd --args -D \
--disp Cygwin sshd --desc Cygwin Openssh service \
--user sshd_server --passwd your_fine_password \
--env CYGWIN=binmode ntsec tty;
# Start the sshd service.
cygrunsrv --start sshd;
# === End of start_sshd.sh === #
Of course, since 'your_fine_password' is provided in clear text, you'll
want to keep this script protected, or maybe change the script to
prompt you for the password.
--
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: 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 21 {
cygrunsrv --stop $service;
cygrunsrv --remove $service;
};
Correction: '$service' should be replaced with 'sshd' in the two
lines above.
--
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/
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 (which has the dual-core processor) connects without error, and the connection is stable. 2. scp is able to copy small binary or text files from the ssh server to the client computer without any timeout errors. Examples: $ scp ssh_server:/bin/ls . ls100% 66KB 66.1KB/s 00:00 $ scp ssh_server:/bin/date . date 100% 38KB 37.7KB/s 00:00 3. scp is unable to copy larger binary files from the ssh server to the client computer. Examples: $ scp ssh_server:/usr/bin/gcc . gcc 0%0 0.0KB/s --:-- ETA Disconnecting: Timeout, server not responding. lost connection $ scp -o ServerAliveCountMax=1500 -o ServerAliveInterval=20 ssh_server:/usr/bin/gcc . gcc73% 64KB 7.8KB/s - stalled - Disconnecting: Timeout, server not responding. lost connection I repeated the above tests using Cygwin's previous version of openssh, 4.3p2-2, the current version of openssh, 4.3p2-3, and the experimental version of openssh, 4.3p2-4. In the examples above, the string 'ssh_server' was replaced by the IP address of the Linux server that is running the ssh service. The Linux server is running openssh-3.6.1p2. The Cygwin client scp was installed for the first time last week, with the Cygwin setup.exe defaults selected for a base installation. Other utility programs that were installed using 'setup.exe' are 'openssh/openssl', 'vim', and 'rxvt'. Cygwin is installed on a computer running Windows XP. I have installed the same version of Cygwin/openssh/etc. on two more computers with dual-core CPUs. Both additional computers have the same problem. I have repeated the commands above without any errors on computers running Windows 2000, 2003, and XP. All computers are connected to the same network. None of the computers on which the above commands ran successfully are using dual-core CPUs. Using the standalone program 'WinSCP', all files listed above can be copied from the server to the client computer without any errors. Has this problem been addressed previously? Is it a known problem with Windows XP running on Intel dual-core processors? Or, does anyone know whether it is a problem with Cygwin running on Windows XP on dual-core processors? I have attached several files to provide more information: 1. The output from the command 'cygcheck -s -v -r' (i.e., cygcheck.txt) 2. A successful copy command using 'scp' with the option '-vvv'. 3. An unsuccessful copy command using 'scp' with the option '-vvv'. If you have any ideas about what might be causing this problem; any ideas about how I can fix it, work around it, or trouble-shoot it; or would like more information about the environment that could help diagnose it, please let me know. Cygwin Configuration Diagnostics Current System Time: Mon May 01 14:45:49 2006 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Program Files\Microsoft SQL Server\80\Tools\Binn\ Output from C:\cygwin\bin\id.exe (nontsec) UID: n(xxx) GID: n() 544(Administrators) 545(Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: n(xxx) GID: n() 544(Administrators) 545(Users) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS USER = 'xxx' PWD = '/home/xxx' HOME = '/home/xxx' MAKE_MODE = 'unix' HOMEPATH = '\Documents and Settings\xxx' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Documents and Settings\xxx\Application Data' HOSTNAME = 'xxx-yyy' TERM = 'xterm' PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 14 Stepping 8, GenuineIntel' WINDIR = 'C:\WINDOWS' WINDOWID = '268905952' OLDPWD = '/c/Documents and Settings/xxx/My Documents' USERDOMAIN = 'yyy' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' !:: = '::\' TEMP = '/c/DOCUME~1/xxx/LOCALS~1/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'xxx' PROCESSOR_LEVEL = '6' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Documents and Settings\xxx' PS1 = '\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\AD05' PROCESSOR_ARCHITECTURE = 'x86' SHLVL = '1' COLORFGBG = 'default;default;0' USERDNSDOMAIN = 'yyy.zzz' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' HOMEDRIVE = 'C:'
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 eliminate the need for creating a batch file if you create a Windows shortcut to 'rxvt'. Once you have created the shortcut, you can edit its properties and change the Target field to use what you have above, that is: C:\cygwin\bin\rxvt -fn Lucida Console-11 -e /bin/bash --login -i Of course, this shortcut may then be dragged to your Windows taskbar or desktop so that you can start rxvt with a mouse-click. Here is my .Xdefaults: [EMAIL PROTECTED]:~$ cat .Xdefaults ! $Id: .Xdefaults,v 1.1 2005/10/18 04:17:23 dpchrist Exp $ XTerm*background: black XTerm*foreground: gray XTerm*colorBD: white XTerm*colorUL: cyan XTerm*saveLines: 1 XTerm*scrollBar_right: True XTerm*scrollTtyKeypress: True XTerm*scrollTtyOutput: True Here are some fonts that I have been able to use in Windows: ~/.Xdefaults: rxvt*font: -outline-Courier New-normal-r-normal-normal-18-96-120-120-c-100-iso8859-1 rxvt*font: -outline-Courier New-normal-r-normal-normal-20-96-120-120-c-100-iso8859-1 rxvt*font: -raster-Fixedsys-normal-r-normal-normal-18-108-120-120-c-100-iso8859-1 Of course, these fonts are mutually exclusive (that is, try each one and decide which one you like). These can be resized with the Shift-Keypad +/- keys. I have also found that under some circumstances, the backspace key does not work properly. The following setting fixed that problem: rxvt*ttyModes: erase ^? Finally, the default size and location can be set in ~/.Xdefaults: rxvt*geometry: 80x35+150+5 --- -- 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: screen
Gary R. Van Sickle wrote: Could somebody *please* explain to me why screen is in any way useful on a system with even a semblance of a window manager? 1. It is useful when the underlying operating system (say, Linux) is more stable than the client operating system (in this case, one of the Windows variants). Using screen, you can connect to multiple servers, have long-lived sessions (weeks), without concern that your session will be terminated when your Windows client computer freezes or needs to be rebooted because of an upgrade. This is another way of saying what Lapo Luchini said, I think. 2. It allows you to create a complex session with multiple screens attached to muliple servers at your favorite computer, disconnect your session from that computer, get up and walk across the office, and reconnect to your session at someone else's computer. 3. If you have an ssh server running somewhere in your network that allows external connections then you can repeat step 2 from anywhere in the world that has internet access. 4. Even if you forget to disconnect (say, when you leave work or when you leave home and return to work), you can list your screen sessions after connecting remotely or locally, and disconnect that session from the other location and connect to it from your new location. 5. Although I haven't had occasion to use it, screen has the ability to allow collaborative work, i.e., multiple people at different locations in an office or around the world could connect to a single screen.
RE: screen
my mistake. I assumed that if experienced people like Gary R. Van Sickle and Lapo Luchini were asking questions and responding on this list, then it was an accepted practice. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED] Sent: Thursday, April 21, 2005 10:40 AM To: [ML] CygWin-Apps Subject: Re: screen On Apr 21 10:28, Harig, Mark wrote: Gary R. Van Sickle wrote: Could somebody *please* explain to me why screen is in any way useful on a system with even a semblance of a window manager? 1. It is useful when the underlying operating system (say, Linux) [...] Nothing personal, guys, but this is *not* the right list to discuss the pros and cons of a tool in such detail. Move to cygwin-talk if you want to discuss this further, please. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc.
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 this started without having reinstalled anything, maybe after an automatic update of the patterns of the antivirus. I attempted to report this problem earlier today, also. For some unknown reason, it did not show up in the mailing list. Here is a copy of the information I have about this possible virus: -Original Message- Sent: Monday, January 10, 2005 10:25 AM To: cygwin list Subject: Possible virus in cygcrypt-0.dll My virus detection software (OfficeScan, version 5.58, engine 7.100, pattern 2.337.00) has detected the virus: BKDR_HACDEF.M in the file cygcrypt0.dll, which is included in the Cygwin package crypt-1.1-1. This has been detected on three PCs, run (independently) by two people. It appears that the problem is localized to the crypt-1.1-1.tar.bz2 file at the rcn.net mirror. Here are the steps that I took to localize the problem after it had been automatically detected by my virus scanning software: 1. Uninstall crypt-1.1-1 using setup.exe. 2. Delete crypt-1.1-1.tar.bz2 from the rcn.net 'release' subdirectory that installation packages are written to. 3. Download/install crypt-1.1-1 from the planetmirror.com mirror using setup.exe. 4. Scan both the 'bin' and 'release' subdirectories for viruses. No viruses were detected. 5. Uninstall crypt-1.1-1 using setup.exe. 6. Delete crypt-1.1-1.tar.bz2 from the planetmirror.com 'release' subdirectory that installation packages are written to. 7. Download/install crypt-1.1-1 from the rcn.net mirror using setup.exe. 8. Scan both the 'bin' and 'release' subdirectories for viruses. The BKDR_HACDEF.M virus is detected in bin/cygcrypt-0.dll and in release/crypt/crypt-1.1-1.tar.bz2. This detection appears to be the result of a new virus pattern file that detects the BKDR_HACDEF.M virus, which earlier versions of the file did not. --- -- 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: 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 the pattern just happened to coincide with the DLL's date stamp -- go figure). I'm half-tempted to suggest leaving the package as-is, just to force people to complain to their anti-virus provider. FWIW, I have done that today (complained to the anti-virus provider). The md5sum for crypt is correct for dowloads from several mirrors, and only after scanning for a virus in the .tar.bz2 file is the md5sum changed. --- -- 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: 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 smtpcons.mof smtpctrs.h Any suggestions? You should be able to find the 'ssmtp' package using setup.exe. It is in the Mail category. --- P.S., Please do not reply to me. Use the mailing list. Please do not include my address in any 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/
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 include my email address in any replies sent to the mailing list.) --- 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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. cron_diagnose.sh Description: cron_diagnose.sh -- 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: 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/printsrv/cygwin-sshd.html. However, I didn' manage on a Windows 2003 server. I always get 1053 did not start in a timely fashion immediately on clicking on the Windows service start button. I tried with both enabling and disabling the privilege separation. I don't think I have to follow the instructions at http://www.cygwin.com/ml/cygwin/2003-09/msg00977.html, since my cygwin version (cygwin DLL version: 1.5.12) already creates a ssd_server user with the privileges mentioned there. Using 'openssh-host-config' is the only documented, supported approach to setting up a Cygwin openssh server. If you follow instructions from other locations, then you need to ask for assistance at those locations. The documentation for the Cygwin-specific openssh setup begins in /usr/share/doc/Cygwin/openssh.README. --- (Please do not reply to me, instead keep all replies on this list. Please do not include my email address in any 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: 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 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
the Bugzilla report, and click on the 'Create new attachment'
link. It will allow you to attach a patch file, and select
that type of file.
---
Please do not reply to me. Please do not include my email
address in any replies to the Cygwin mailing list.
-Original Message-
From: William R. Knox
Sent: Tuesday, November 30, 2004 12:38 PM
Subject: Patch to /etc/profile to deal with $HOME with a space
I have just set up Cygwin, and noticed that my default home
was under my
Documents and Settings directory (not yet having run
mkpasswd). However,
the /etc/profile setup which tries to only create the warning message
about running mkpasswd and mkgroup once can't deal with a
HOME environment
variable with a space in it. Here is a patch to allow that to work:
--- /etc/profile2004-11-26 14:53:34.477082000 -0500
+++ /etc/profile2004-11-30 11:22:32.175340300 -0500
@@ -194,10 +194,10 @@
echo and can be safely ignored.
# only display the above once
- cp -f /etc/group ${HOME}/group.mkgroup_l_d \
+ cp -f /etc/group ${HOME}/group.mkgroup_l_d \
( [ -w /etc/group ] || chmod --silent a+w /etc/group ; )\
- sed -e 's/^mkgroup_l_d/mkgroup-l-d/'
${HOME}/group.mkgroup_l_d /etc/grou
p \
+ sed -e 's/^mkgroup_l_d/mkgroup-l-d/'
${HOME}/group.mkgroup_l_d /etc/gr
oup \
chmod --silent --reference=/etc/passwd /etc/group
- rm -f ${HOME}/group.mkgroup_l_d
+ rm -f ${HOME}/group.mkgroup_l_d
;;
esac
--
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: 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 the Bugzilla report, and click on the 'Create new attachment' link. It will allow you to attach a patch file, and select that type of file. If you have not used Bugzilla before, then it will require that you create an account. This requires that you provide your email address and name. Bugzilla will send a password to your email account. After you log in using this cryptic password, you can change it to something you can remember by clicking on the 'prefs' link in the footer. For a new account, click on the 'Open a new Bugzilla account' at the URL http://sources.redhat.com/bugzilla/. Please do not reply to me. Please do not include my email address in any replies to the Cygwin mailing list. --- -- 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: 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 the Bugzilla report, and click on the 'Create new attachment' link. It will allow you to attach a patch file, and select that type of file. Didn't we say that before? Please don't file arbitrary patches to bugzilla by yourself! Let the developers do that, based on the discussion here. -- Reini Urban OK. Should this be added to http://cygwin.com/problems.html? Or, should subscribers to this list not be referred to Bugzilla? -- 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: 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 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 the Bugzilla report, and click on the 'Create new attachment' link. It will allow you to attach a patch file, and select that type of file. Didn't we say that before? Please don't file arbitrary patches to bugzilla by yourself! Let the developers do that, based on the discussion here. -- Reini Urban OK. Should this be added to http://cygwin.com/problems.html? Or, should subscribers to this list not be referred to Bugzilla? Also, does http://cygwin.com/contrib.html need to be updated in light of the use of Bugzilla, or is it still the preferred way to provide patches? From the contrib.html page: When you have finalized your changes Once you've finished making and testing your changes, you should send a unified diff to the cygwin-patches list. As an example, if you have modified several files in /c/src/winsup, then do the following in bash: cd /c/src/winsup cvs diff -up /tmp/mypatch This will produce one file with all of your changes, making it easy for someone to review and apply. Send the contents of this file as plain text. Do not uuencode or otherwise encrypt it. Then send it to the cygwin-patches list in an email along with an explanation of what the change does. Make sure that you include a ChangeLog entry. If you have never used a ChangeLog before 1) refer to the GNU ChangeLog Standards and 2) model your entry after other entries in the file winsup/ChangeLog. - -- 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: 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 script has
not completed
properly. I'd run /etc/postinstall/man.sh and then rename it to
/etc/postinstall/man.sh.done. If the only thing you have is
/etc/postinstall/man.sh.done, then that's the script that
you'll need to
re-run (don't worry about the timestamp, it doesn't have to
be after the
install time). When you copied the default config file, you
did part of
the job of that postinstall script (AFAICS, creating
manpath.exe is the
other part, hence the question).
It's possible that he had the same problem I did,
which is that /usr/share/misc/man.conf did not have
write permission turned on (and so the file copying
operation failed).
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/man.conf ] ; then
chmod 644 ${datadir}/misc/man.conf
cp ${datadir}/misc/man.conf.default ${datadir}/misc/man.conf
fi
--
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: 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/man.conf ] ; then
chmod 644 ${datadir}/misc/man.conf
cp ${datadir}/misc/man.conf.default ${datadir}/misc/man.conf
fi
Actually, this suggestion does not help because of
the 'if [ ! -e ${datadir}/misc/man.conf ]' guard.
My old man.conf was obsolete (had errors), but it
was the default at the time (I have never changed it).
Other users may run into this problem and need to apply
the suggested fix (i.e., overwrite /usr/share/misc/man.conf
with /usr/share/misc/man.conf.default, after adding write
permission to /usr/share/misc/man.conf).
---
--
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: 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. -Original Message- From: Igor Pechtchanski Sent: Wednesday, November 24, 2004 12:06 PM Subject: RE: Upgraded man command There's always the solution that base-files uses for replacing various config files -- it checks whether the file is the same as the default in the preremove script, and erases it if so. Then the postinstall script copies the new default, and the config file is up-to-date. This won't work if the users edited their config files, but should work in most cases. OK. I will submit a bug report suggesting that /etc/preremove/base-files-manifest.lst be updated to include /usr/share/misc/man.conf. --- -- 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: 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-contained, we should add the same logic that's in /etc/preremove/base-files.sh to /etc/preremove/man.sh. I submitted a bug report (#571). It mentions the possible (unintentional) dependency. Incidentally, the code that looks through the manifest file and does the comparisons can be factored out to something like /etc/preremove/remove-defaults.sh, and then invoked from both man.sh and base-files.sh as /etc/preremove/remove-defaults.sh /etc/preremove/man-manifest.lst or /etc/preremove/remove-defaults.sh /etc/preremove/base-files-manifest.lst, respectively. Unless we ever get a package called remove-defaults, this should be safe to do. The actual script can be part of the base-files package (once setup is changed to run all preremove scripts first, before removing package contents). The creation of /etc/preremove/man-manifest.lst and factoring out common code sounds like a good idea to me. Please feel free to add this suggestion to Bug #571, if you want, or to create a new report. --- -- 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: /etc/profile error
http://cygwin.com/ml/cygwin-apps/2004-11/msg00106.html 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 application I downloaded from the Cygwin site. Also, I customized this installation substantially. kj -- Simply let 'setup.exe' install it as you have been. The next update to base-files (version 3.1-4) fixes the problem that you have been seeing in /etc/profile. The installer (setup.exe) will install a new copy of /etc/profile. -- 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: 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 wasn't long before being ^A^Z trigger happy drove me nuts, and I made my own patch that disabled the suspend and detatch (which is broken under cygwin) keystrokes. http://www.alphalink.com.au/~ord/home/cygwin.html I'm happy for someone to run with my patch and add it to the cygwin distro. If not I could possibly handle the package, depending how time consuming it'd be. My guess is that this should start with: http://www.gnu.org/software/screen/ And then add patches as necessary to get this to work on Cygwin. --- -- 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: 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., Please reply directly to this mailing list and not to me. Also, please do not include my email address in the reply. -- 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: 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 older cygwin1.dll version: 1.5.11-snapshot-20040720-12:03:09. I concur. It appears to be a bug in cron, or Cygwin's version of cron. Can anyone point to some documentation which states that cron is supposed to gracefully handle date changes? Personally, I've always restarted cron after a date change since I've noticed behavior like this on linux in the past. If that has been fixed, however, that would be an interesting data point for linux (off-topic) and cygwin (on-topic). The original problem (cron is not running over the course of a 24-hour date change) is not a Cygwin-specific problem, i.e., Cygwin's cron appears to work when asked to perform a task once a day at a specified time. I wrote a simple cron table entry 1 1 * * * /usr/bin/date /tmp/date.txt 'cron' ran this task for me for the past three days without errors or intervention. I do not know whether the secondary problem (cron fails to run without a restart if there has been a date change outside of the normal clock) is cron specific or Cygwin specific. --- -- 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: 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 steps to take if it is unable to detect any problems P.S., Please reply directly to this mailing list and not to me. Also, please do not include my email address in the reply. -- 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: 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 older cygwin1.dll version: 1.5.11-snapshot-20040720-12:03:09. I concur. It appears to be a bug in cron, or Cygwin's version of cron. The following fails to work correctly for me: 1. Create the following crontab entry: * * * * * /usr/bin/date /tmp/date.txt 2. Start cron as a service and wait one minute. Cron adds a line to /tmp/date.txt. 3. Using Windows's Adjust Date/Time applet, set the date to the previous day. 4. Wait one minute, and cron adds another line to /tmp/date.txt. 5. Using Windows's Adjust Date/Time applet, set the date to the current day. 6. Wait one (or more) minute, and cron does NOT add another line to /tmp/date.txt. Cron should resume updating /tmp/date.txt. If I stop the cron service and restart it, then cron resumes updating /tmp/date.txt. --- -- 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: 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 postinstall/exim.sh.done) Pierre As I reported earlier, there are already two tests for this. Please see lines 254 through 272 of version 1.7 of cron_diagnose.sh. I must be misunderstanding this problem because I cannot see why these tests do not detect the error condition. --- -- 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: 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.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 steps to take if it is unable to detect any problems For what it is worth, crond is working on both Win2K and WinXP for me. I've tried updating my passwd (I live on a Win2K server domain) file in case it was out of date or missing local users (vs domain users), using $ mkpasswd -d -l -g /etc/passwd The following commands should give you a simple, and possibly valid, password file: $ mv /etc/passwd /etc/passwd.save $ mkpasswd -l /etc/passwd $ mkpasswd -d -u [your Windows user ID] /etc/passwd You would edit your entry then if you wanted to change your login shell, home directory, group, etc. --- -- 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: 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 earlier releases, which you are running. http://cygwin.com/ml/cygwin/2004-08/msg00633.html -- 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: 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
'GetVolumeInformation() failed')
From your cygcheck.txt:
] Output from D:\cygwin\bin\id.exe (ntsec)
] UID: 14919(SPI) GID: 12385(mkgroup_l_d)
] 544(Administrators) 545(Users)
] 12385(mkgroup_l_d)
It looks as though you have not set up your /etc/group file
and 'group' entry for your user account (ID 14919) in your
/etc/passwd file. Please see the documentation for the
'mkgroup' command ('man mkgroup' and 'mkgroup --help').
--
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: 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't find it . This is defined in Cygwin's /etc/passwd file. You will want to generate a password file with some variation of the 'mkpasswd' command: $ /usr/bin/mkpasswd -l /etc/passwd or $ /usr/bin/mkpasswd -d -u gurkan /etc/passwd and then edit /etc/passwd, and change the second-to-last field so that it contains the HOME directory that you want. Similarly, you will want to use the 'mkgroup' command to generate a useable /etc/group file, for example, $ /usr/bin/mkgroup -l /etc/group -- -- 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: 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 that you have started, i.e., a no-window version, unless you have installed the Cygwin distribution of the X Windows software. -Original Message- From: Richard Heintze [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 4:30 PM To: [EMAIL PROTECTED] Subject: HOw to install emacs? I've been downloading emacs from the gnu site and running addpm.exe to install it on Windows 2003. I notice there is an emacs in the cygwin distribution but I cannot figure out how to run it. Do not I need to run addpm.exe like I do in the GNU distribution? I cannot find this program in the cygwin distribution. Thanks, Siegfried __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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/ -- 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/
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. return 1 fi done I have -rw-r--r--+ which should be checked. Or is it a new requirement that no extended ACL must be defined? To my knowledge not. So please delete the last space in the regex. Thank you for the bug report. I have changed the regular expression match to look for an optional trailing '+' before the space. Attached below is version 1.7 of this diagnostic script. --- 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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. cron_diagnose.sh Description: cron_diagnose.sh -- 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/
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. Although they are created, these elements can get deleted. Attached below is version 1.6 of the script. The update in this version adds a message recommending that the user examine cron's log file. --- 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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. cron_diagnose.sh Description: cron_diagnose.sh -- 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: 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 command line, but when I try to execute them from cron the sciripts are executed, but the runmqsc command reports that it can't connect to the queue manager. Has anybody come across this or similar problems? If so how were they resolved? (I hace searched the archives, but can find no reference to this type of problem) You might try examining your environment variables: * * * * * /usr/bin/env /tmp/env.txt The environment variable settings that are set by default within cron is a limited set. For more information, see man 5 crontab. -- 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: 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 running as the SYSTEM account which didn't have permissions to overwrite the file. The solution would be to either just remove it and let cron recreate it, or chown SYSTEM:SYSTEM /var/run/cron.pid. Then you could give it more restrictive permissions than 777, perhaps 640 or 600. At present, the diagnostic script only checks for the existence of /var/run/cron.pid and, if found, suggests that the user delete it before reinstalling/restarting the cron service. I agree that the script should check for SYSTEM.SYSTEM ownership and 640 permissions, but I have not been able to find any documentation specifying this. Can anyone please point me to some that specifies what the ownership and permissions of cron.pid should be? Of course, if users simply do what cron_diagnose.sh suggests today, that should resolve this particular problem (i.e., not being able to write to the cron.pid file). --- -- 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: 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 displaying the log file. Is this correct? I am hesitant to display the contents of the log file because it adds to the text displayed, and there have been a number of problems reported simply because users do not read the output of the script carefully. In addition, the log can get long. --- -- 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: 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 problems Quoting Harig, Mark [EMAIL PROTECTED]: -- 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: 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:12 PM
To: cygwin
Subject: CRON problems
Hello,
I've been doing my best to read all the previous FAQ pages,
README documents,
and forum posts, but I am still having issues getting my cron
jobs to run the
way I want them to. If I explicitly start cron by calling
/usr/sbin/cron, then
my jobs run fine, but my application demands that the
computer be rebooted
daily and I will not be onsite to issue this comand. I would
like cron to start
up after reboot automatically and if I understand correctly, this is
accomplished by following the instructions in
cron_diagnose.sh which describe
how to shutdown the cron service, uninstall it, reinstall it
and start it.
Everything works just fine except for starting the service,
when I run:
cygrunsrv -S cron. I get this error message:
cygrunsrv: Error starting a service: QueryServiceStatus:
Win32 error 1062:
The service has not been started.
After reading through some more posts I have become
thoroughly confused, so I
have resorted to asking for help.
The output from cron_diagnose.sh is:
cron_diagnose.sh 1.2
This script did not find any errors in your crontab setup.
If you are still unable to get cron to work, then try
shutting down the cron service, uninstalling it,
reinstalling it, and restarting it.
The following commands will do that:
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
$ cygrunsrv --start cron
If none of this fixes the problem, then report your problem
to [EMAIL PROTECTED] Please include a copy of your crontab,
('crontab -l') and the output of 'cygcheck -srv cygcheck.txt'.
PLEASE include the generated files 'cygcheck.txt' *as an attachment*,
and NOT in the body of the mail message.
My crontab looks like this:
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.1244 installed on Wed May 5 23:57:19 2004)
# (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41
corinna Exp $)
53 21 * * * shutdown -r -f now
58 * * * * tcsh /home/stats/Trans/programs/hourly_mover.tcsh
03 22 * * * tcsh /home/stats/Trans/programs/daily_mover.tcsh
Thanks in advance for your help. I have attatched
cygcheck.txt as instructed.
Hank
--
--
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: 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 run it several times. It stops each time it finds a problem. -Original Message- From: John Joganic Sent: Wednesday, May 05, 2004 4:51 PM To: cygwin Subject: 1.5.9: cron hangs on 2003 server Bash scripts that run normally from the command line hang periodically in cron. Is there a specific diagnostic approach for this class of problem? The server has 3.3GB of 4GB free memory and the max heap size is 1GB per the User Guide. The same script runs correctly on other cygwin installations. Only the 2003 Server does not run consistently. Any help, observations, or referrals would be greatly appreciated, and I can provide more information as needed. I should also add that the script in question is not considered the culprit. Logging from within the script shows that it hangs in arbitrary places. The cygcheck.out file is attached with some names changed to protect the innocent. John Joganic Prime Analytics -- 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: 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)' Cc: Subject: RE: Unable to get CRON to work Thank everybody. I have installed script cron_diagnose.sh, and run it. In fact, the cron service was not installed ! :o(( So, after the cygrunsrv --install... command, the crontab is running. :oD After your messages, I modified users and groups, and my system seems to be clean. Thanks a lot ! Frederic -- 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: Unable to get CRON to work
1. Please send all replies to the mailing list. This could help to get your problem resolved more quickly because more people will be able to see your problem description. 2. I did not see any mention in your message below that you had run the cron_diagnose.sh script. This script will NOT change anything on your computer, and it should help to find many common problems. The intent of this script is to help reduce the number of messages sent to the mailing lists that are just repetitions of things that people should try when installing/using cron. You may find a copy of this script here: http://sources.redhat.com/ml/cygwin/2004-03/msg00379.html Please download this (small) script, run it, and read its results. Each time is finds a problem, it stops to provide information to the user. You may have to re-run it several times to find all of the problems with your setup. Please read its results carefully, even if it says it can find NO problems. 3. From your message below, it looks as though you are still logged on as the Administrator. Are you logged on to Windows as 'administrator'? If so, then you might want to log off and log on as an ordinary user. Alternatively, if you are already logged on as an ordinary user, then did you start a second window / bash session after you made the changes to /etc/passwd and /etc/group? The changes you made to those files do not take effect until 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 of context of mailing list. Did you resolv your problem of crontab ? So maybe can you bring me good help... I've got the same problem, and it would be so stupid to give up cygwin because of that. I passed command mkgroup -l /etc/group and mkpasswd /etc/passwd $ cat /etc/group root:S-1-5-32-544:0: SYSTEM:S-1-5-18:18: Aucun:S-1-5-21-796845957-823518204-725345543-513:513: Administrateurs:S-1-5-32-544:544:Administrateur Duplicateurs:S-1-5-32-552:552: Invités:S-1-5-32-546:546:Invité,TsInternetUser Opérateurs de sauvegarde:S-1-5-32-551:551: Utilisateurs:S-1-5-32-545:545:sshd Utilisateurs avec pouvoir:S-1-5-32-547:547: $ cat /etc/passwd SYSTEM:*:18:544:,S-1-5-18:: Administrateurs:*:544:544:,S-1-5-32-544:: Administrateur:unused_by_nt/2000/xp:500:547:U-CSOCMCAWCG\Admin istrateur,S-1-5-21-796845957-823518204-725345543-500:/home/Adm inistrateur:/bin/bash Invité:unused_by_nt/2000/xp:501:513:U-CSOCMCAWCG\Invité,S-1-5- 21-796845957-823518204-725345543-501:/home/Invité:/bin/bash sshd:unused_by_nt/2000/xp:1001:513:sshd privsep,U-CSOCMCAWCG\sshd,S-1-5-21-796845957-823518204-7253455 43-1001:/var/empty:/bin/bash TsInternetUser:unused_by_nt/2000/xp:1000:513:TsInternetUser,U- CSOCMCAWCG\TsInternetUser,S-1-5-21-796845957-823518204-7253455 43-1000:/home/TsInternetUser:/bin/bash The cron file Administrateur beyongs Administrateur's user : [EMAIL PROTECTED] /var/cron/tabs $ ls -al total 1 drwxrwxrwt+ 2 Administ Utilisat0 Apr 21 20:18 . drwxrwxrwt+ 3 Administ Utilisat0 Apr 9 18:23 .. -rwxrwxrwx1 Administ SYSTEM329 Apr 21 20:18 Administrateur And in desesperation, I put all rights (777) to this file, but nothing's is efficient. Please, what is the best solution to activate the cron fonction ? Scuse for my bad english langage... ;o) Fred. -- 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: 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. I have run the cron_diagnose.sh program and it told me to run a cygcheck. Output from both are attached. From your attached text: $ ls -ltr /cygdrive/h total 200 -rw-r--r--1 sacharb mkgroup- 201884 Sep 4 2001 impacddl.zip Notice that the group ownership is set to 'mkgroup-'. This indicates that your entry for 'sacharb' has not been setup completely in your /etc/passwd and /etc/group files. This is further indicated from your attached text: Output from C:\cygwin\bin\id.exe (nontsec) UID: 25016(sacharb) GID: 10545(mkgroup-l-d) 10545(mkgroup-l-d) Output from C:\cygwin\bin\id.exe (ntsec) UID: 25016(sacharb) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 545(Users) 1005(ORA_DBA)10545(mkgroup-l-d) The GID: 10545(mkgroup-l-d) is telling you to run the mkgroup command to update your /etc/group file (and make a corresponding change to your entry in your /etc/passwd file). Please see the documentation in the manual pages for the 'mkpasswd' and 'mkgroup' commands, i.e., run man mkpasswd and man mkgroup. -- 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: cron will not execute commands
Steve, Please send all replies to the Cygwin mailing list. This will help because more people will be able to see your problem and may be able to help to come up with a solution. Also, it may help other people reading and searching this list if they have this problem or a similar problem. From your cygcheck.txt: Output from C:\cygwin\bin\id.exe (nontsec) UID: 10500(Administrator) GID: 10545(mkgroup-l-d) 10545(mkgroup-l-d) Output from C:\cygwin\bin\id.exe (ntsec) UID: 10500(Administrator) GID: 10545(mkgroup-l-d) 544(Administrators) 545(Users) 10545(mkgroup-l-d) 1. You do not appear to have created a 'group' entry for your account, as seen from your GID. The text in parentheses, 'mkgroup-l-d', is a short-hand for telling you to run the 'mkgroup' utility with either the '-l' (local) or '-d' option. Type 'man mkgroup' for more details. 2. Your account appears to be the Administrator. You likely want to create an account under your user ID (type 'man mkpasswd' for details), and then restart your bash session. 3. After setting up a personal account, you will likely want to run 'ssh-user-config' 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 execute commands Mark: Thanks for the reply:) I was able to get cron to output the date to date.txt in tmp and it created a file env.txt, but cron will not execute the rsync command. It works from the command line, but not from cron. I have included cygcheck.txt, crontab.txt, and messages.txt. Could you take a look at this to see if you can help me solve my problem? I am trying to have cron run an rsync command to copy the contents of /BACKUPS on 10.10.10.9 after its nightly backup. Cgywin is running on 10.10.10.4, and 10.10.10.9 is a RedHat box running RH-9.0. Thanks in advance for you help. Steve Nutt -Original Message- From: Harig, Mark Sent: Wednesday, March 10, 2004 7:45 AM To: steve; [EMAIL PROTECTED] Subject: 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 with the specific commands that you want run. Please try a simple crontab entry such as the following to establish that cron is running: * * * * * /usr/bin/date /tmp/date.txt 3. Verify that the environment that cron sees is adequate for what your program needs: * * * * * /usr/bin/env /tmp/env.txt Hello:) To whom It may concern- I am trying to have cron execute a simple rsync command, but have run across substantial problems trying to make it work. I have rtfm documentation - user guide, FAQ, Google and mail archives when I came across this http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html I have run the cron_diagnose.sh and followed the suggestion done it twice so now I am sending you this. By the way it works fine from the command line. I have also included the messages.txt from tail -f /var/log/messages for this crontab. Will someone respond to this? Need help. Thanks: Steve Nutt Cygwin Win95/NT Configuration Diagnostics Current System Time: Mon Mar 22 18:48:28 2004 Windows XP Professional Ver 5.1 Build 2600 Service Pack 1 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Program Files\Common Files\Roxio Shared\DLLShared Output from C:\cygwin\bin\id.exe (nontsec) UID: 10500(Administrator) GID: 10545(mkgroup-l-d) 10545(mkgroup-l-d) Output from C:\cygwin\bin\id.exe (ntsec) UID: 10500(Administrator) GID: 10545(mkgroup-l-d) 544(Administrators) 545(Users) 10545(mkgroup-l-d) SysDir: C:\WINDOWS\System32 WinDir: C:\WINDOWS HOME = `c:\Documents and Settings\administrator.HELIOS1' MAKE_MODE = `unix' PWD = `/cygdrive/c/Documents and Settings/administrator.HELIOS1' USER = `Administrator' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\administrator.HELIOS1\Application Data' CLIENTNAME = `Console' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `JUPITER' COMSPEC = `C:\WINDOWS\system32\cmd.exe' CVS_RSH = `/bin/ssh' HOMEDRIVE = `C:' HOMEPATH = `\Documents and Settings\administrator.HELIOS1' HOSTNAME = `jupiter' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:' LOGONSERVER = `\\W2K-DELL' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr
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 a problem, it stops and displays a descriptive message. Please read the messages that the script generates, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. - cron_diagnose.sh Description: cron_diagnose.sh -- 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: 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,
I have trouble getting my cron to work. I have tried cron_diagnosis.sh
1.3 but I could not find any problems. I also did the suggestion from
the cron_diagnosis.sh output but it does not work. Here is the crontab
-l, cron_diagnose.sh output and the cygcheck -srv output. Hope you can
help me.
% 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
%
-- output of cron_diganose.sh --
% bin/cron_diagnose.sh
cron_diagnose.sh 1.3
This script did not find any errors in your crontab setup.
If you are still unable to get cron to work, then try
shutting down the cron service, uninstalling it,
reinstalling it, and restarting it.
The following commands will do that:
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
$ cygrunsrv --start cron
If the cron service does not start, try deleting the file
/var/run/cron.pid and then repeating the commands above.
If none of this fixes the problem, then report your problem
to [EMAIL PROTECTED] Please include a copy of your crontab,
('crontab -l') and the output of 'cygcheck -srv cygcheck.txt'.
PLEASE include the generated files 'cygcheck.txt' *as an attachment*,
and NOT in the body of the mail message.
--
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: 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' -- you
are instructing cron to execute the date
string. Simply use:
* * * * * date /usr/tmp/date.txt
--
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/
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 does report one when it should. --- 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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. - cron_diagnose.sh Description: cron_diagnose.sh -- 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: 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 PROTECTED] Sent: Tuesday, February 24, 2004 4:06 PM To: [EMAIL PROTECTED] Subject: Cron Running As UID 400 Hi, I've been through a couple of problems already with cron and have resolved all of them (thanks to this list!) except this last one. The cron service is indeed running, but no jobs are ever run as described in the crontab. A strange thing I've noted is that the user that the cron service is running under is not the expected SYSTEM but the unknown 400 as: $ ps -ef UID PIDPPID TTY STIME COMMAND winwa02 904 1 ?Feb 23 /usr/X11R6/bin/XWin SYSTEM3912 1 ?Feb 23 /usr/bin/cygrunsrv SYSTEM15123912 ?Feb 23 /usr/sbin/inetd SYSTEM2616 1 ?Feb 23 /usr/bin/cygrunsrv SYSTEM26482616 ?Feb 23 /usr/sbin/cygserver winwa021412 1 4Feb 23 /usr/bin/rxvt winwa0235521412 5Feb 23 /usr/bin/bash winwa0230843552 5Feb 23 /usr/bin/telnet winwa023228 1 2 14:16:18 /usr/bin/rxvt winwa0236403228 3 14:16:19 /usr/bin/bash winwa0231763640 3 15:46:35 /usr/bin/telnet winwa023016 1 6 16:06:23 /usr/bin/rxvt winwa0225043016 7 16:06:23 /usr/bin/bash winwa023856 1 0 11:13:47 /usr/bin/rxvt winwa0235763856 1 11:13:48 /usr/bin/bash 4002228 1 ? 12:30:59 /usr/bin/cygrunsrv 400 5362228 ? 12:30:59 /usr/sbin/cron winwa0221882504 7 12:37:47 /usr/bin/ps Note that other cygrunsrv processes do indeed correctly run under SYSTEM. I suspect that if my cron and its associated parent cygrunsrv process were running as SYSTEM, then the cron jobs would execute per the crontab. In fact, I manually ran /usr/sbin/cron as my user (winwa02) and cron was indeed able to kick off the crontab jobs properly. A relevant entry in the Windows XP Application Event log appears in full when /usr/sbin/cron starts as: The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: /usr/sbin/cron : PID 536 : (winwa02) ORPHAN (no passwd entry). The typical command line used to install the cron service was: cygrunsrv -I cron -p /usr/sbin/cron -a -D -e CYGWIN=tty ntsec -d CYGWIN cron My domain /etc/passwd and /etc/group files are up-to-date. As usual the output of the relevant sections of cygcheck -svr appears below: Cygwin Win95/NT Configuration Diagnostics Current System Time: Tue Feb 24 11:08:08 2004 Windows XP Professional Ver 5.1 Build 2600 Service Pack 1 --snip-- Output from C:\cygwin\bin\id.exe (nontsec) UID: 5120(winwa02) GID: 10513(Domain Users) 10513(Domain Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 5120(winwa02) GID: 10513(Domain Users) 544(Administrators) 545(Users)143344(442-SC-CRO-R) 106908(98-Site) 10513(Domain Users) 162415(NASiteGroups) 169978(North American Sites) SysDir: C:\WINDOWS\System32 WinDir: C:\WINDOWS CYGWIN = `tty notitle glob ntsec codepage:oem server' HOME = `C:\cygwin\home\winwa02' MAKE_MODE = `unix' PWD = `/home/winwa02' USER = `winwa02' --snip-- 1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 cygwin1.dll v0.0 ts=2004/1/30 16:32 Cygwin DLL version info: DLL version: 1.5.7 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 109 Shared data: 3 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Fri Jan 30 19:32:04 EST 2004 CVS tag: cr-0x9e Shared id: cygwin1S3 --snip-- Cygwin Package Information Last downloaded files to: C:\Documents and Settings\winwa02\My Documents\My Downloads\cygwin Last downloaded files from: ftp://mirrors.rcn.net/pub/sourceware/cygwin Package Version -- snip -- cron
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 detected, it recommends that the user perform the steps that you took above. -- 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: 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] Sent: Thursday, February 19, 2004 4:56 AM To: [EMAIL PROTECTED] Subject: Running cygwin cron under WinXP SP1 I have just installed the latest cygwin and set up cron to run using cygrunsrv -I cron -p /usr/sbin/cron -a -D cygrunsrv -S cron It is running as a service (both in XP task manager and in ps -ef) But I can't get it to execute commands. I have tried a crontab as both /etc/crontab and /var/cron/tabs/Russell Is there an FAQ for getting cron running under cygwin? I can't been able to find one. Thanks Russell -- 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/ -- 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: 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: Friday, January 30, 2004 12:34 PM
Subject: what's the best venue for help with the cygwinized emacs?
Is there some list that the {developer, maintainer}(s) of the cygwin
patches for emacs listen to? Is there a support site? If not, I'm
wondering whether to go to this list, another of the cygwin lists, or
one of the emacs lists (e.g. help-emacs-windows)--but I want to know
in which list(s) such queries are actually serviced, not merely what
folks feel is most appropriate.
--
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: 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 could either create a shell function or alias to reduce typing. -Original Message- From: Christian [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 9:51 AM To: Gerrit P. Haase Cc: Christian; cygwin Subject: Re: error 1062 when starting distccd Gerrit P. Haase schrieb: Hallo Christian, Hi Gerrit! I have read the docu and think, that i've installed the distccd-service in the right way. When starting the service with cygrunsrv.exe -S distccd, the log says: PID 672 : starting service `distccd' failed: execv: 0, No error. -- 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: 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/distccd.pid Stop distccd - if [ -f /var/run/distccd.pid ]; then kill -s SIGTERM $(cat /var/run/distccd.pid); fi You could either create a shell function or alias to reduce typing. -- 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: 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 PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: cron + network share(w/ full access?) Hello and Happy New Year. Would it be possible to see your altered /etc/passwd? I must be doing something wrong. I've made my user have uid 18, put his entry before SYSTEM, and I still get the same 1062 error when starting the cron service as that user. I've been banging my head against the wall on the cron-job-accessing-network-shares problem for a couple days now :) I'm glad I found this thread, it's given me some hope. Can anyone verify that they've got this trick/hack to work in the current version of cygwin cron? Thanks in advance, Alan Right. Looks like 18 is hardwired in cron. So after you create that user and update the /etc/passwd file you would need to edit /etc/password and change the uid of the user to 18. With a little bit of luck the setuid(18) will be a noop. Try keeping the SYSTEM uid to 18, too, for now. It's probably hardwired too. My head is spinning and I don't have the time to sort through all the implications. ok, changing the uid to 18 in the passwd file did it. thanks a lot! thanks to all the Cygwin developers, it's a fantastic tool! --tim __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ -- 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/ -- 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/
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 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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. - cron_diagnose.sh Description: cron_diagnose.sh -- 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: Windows 2003 Server Cygwin Cron
1. Permissions for /var/cron/tabs/user ID 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 Message- From: Benn Schreiber [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 11:51 AM To: [EMAIL PROTECTED] Subject: Re: Windows 2003 Server Cygwin Cron I am running on Windows 2003 server, and set up cron_server per this note. The cron server starts just fine, but reports that it can't open tabs/theuser (where theuser is the user account name). The protection on tabs/theuser is 640 o.g is user.SYSTEM which is probably why cron server can't open it. I changed the group to administrators, which cron_server is part of, but unfortunately, a 'crontab -e' resets the group to SYSTEM. Thanks Benn From: Corinna Vinschen corinna-cygwin at cygwin dot com To: cygwin at cygwin dot com Date: Tue, 11 Nov 2003 10:02:53 +0100 Subject: Re: Windows 2003 Server Cygwin Cron References: [EMAIL PROTECTED] Reply-to: cygwin at cygwin dot com On Mon, Nov 10, 2003 at 03:26:07PM -0700, Brian Cruikshank wrote: I have tried putting the everyone group on the Local Security policies for Create a token object, Logon as service, and Replace a process level token. The problem still happens. URGH! Don't do this. Remove the Everyone group from these rights again. The easiest way is to follow the ssh-host-config script in creating a special account: net user cron_server passwd /add /yes net localgroup administrators_group_name cron_server /add editrights -a SeAssignPrimaryTokenPrivilege -u cron_server editrights -a SeCreateTokenPrivilege -u cron_server editrights -a SeIncreaseQuotaPrivilege -u cron_server editrights -a SeServiceLogonRight -u cron_server mkpasswd -l -u cron_server /etc/passwd For security reasons: editrights -a SeDenyInteractiveLogonRight -u cron_server editrights -a SeDenyNetworkLogonRight -u cron_server editrights -a SeDenyRemoteInteractiveLogonRight -u cron_server And then create a cron service using that account: cygrunsrv -I cron -p /usr/sbin/cron -a -D -u cron_server -w passwd By the way, I see reference to a cron README file that should have been in the install. I cannot find it anywhere yet. Did it get lost in the new releases or is it hiding somewhere other than /usr/doc? /usr/share/doc/... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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/ -- 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: 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 on Windows 2000 SP3 I do not know what is causing your problem, but I reproduced the two Makefiles and the directory tree. 'make' gave the expected results instead of the erroneous results that you are seeing. Are you running ash (/bin/sh), bash, or some other shell? Here is what I am running: $ cygcheck -c ash bash cygwin make Cygwin Package Information Package VersionStatus ash 20031007-1 OK bash 2.05b-16 OK cygwin 1.5.5-1OK make 3.80-1 OK This is on Windows 2000. You might try checking your installation with 'cygcheck -c' and consider reinstalling some packages. - -- 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: 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: $ mkpasswd -u gpontavice -l /etc/passwd or $ mkpasswd -u gpontavice -d /etc/passwd What does 'ls -ln' show in your 'fold' directories? -- 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 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-config' script that is provided with OpenSSH (in /usr/bin). This should allow you to do the minimal amount of configuration. Then copy the public-key file that it creates in your ~/.ssh directory to the ssh server machine's ~/.ssh directory. 2. Or, describe the steps that you took to create your ssh client configuration. -- 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: 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: Michael Lemke [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 5:58 PM To: [EMAIL PROTECTED] Subject: where is g77? I just tried to use g77. It's not there! I checked my gcc-3.3.1-3.tar.bz2 file and no trace of it. It used to be in the gcc package, where did it go? I need it back! Thanks, Michael -- 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/ -- 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: 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 feedback. The cron_diagnose.sh script does check for /etc/cron.d, and does check to see that it is a directory with the proper permissions (a minimum of 'rx' for the owner). You might have an earlier version of the script? It reports its version when it is run. The latest version is 1.2. -- 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/
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, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it. - cron_diagnose.sh Description: cron_diagnose.sh -- 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: Need help with password-less ssh
[EMAIL PROTECTED] ~/.ssh $ ssh-keygen -t rsa -f $HOME/.ssh/id_rsa Generating public/private rsa key pair. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/jware/.ssh/id_rsa. Your public key has been saved in /home/jware/.ssh/id_rsa.pub. The key fingerprint is: fingerprint remove Because you are generating the newer 'id_rsa/id_rsa.pub' key-pair instead of the older 'identity/identity.pub' key-pair, you need to copy your 'id_rsa.pub' file to the newer '.ssh/authorized_keys2' file, instead of the older '.ssh/authorized_keys'. Also, check to make sure that on both the client and server computers your '.ssh' directory is readable only by you (mode: 700), and that the 'authorized_keys2' file on the server computer is write-able only by you (mode: 644). -- 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: Can I read the name of a shell function?
Please provide an example of what you are doing, along with what results you are getting, and what results you expect. -Original Message- From: zzapper [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 7:18 AM To: [EMAIL PROTECTED] Subject: Can I read the name of a shell function? HiYaAll I have created a lot of functions in my .profile When I try to read the function name from within the function $0 just returns bash. Is there any way of reading the functions name?? zzapper -- vim -c :%s/^/WhfgTNabgureRIvzSUnpxre/|:%s/[R-T]/ /Ig|:normal ggVGg? http://www.vim.org/tips/tip.php?tip_id=305 Best of Vim Tips -- 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/ -- 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: Testers for new ssh-*-config scripts wanted!
I will read these two scripts soon. This won't be a thorough test, but it will be another set of eyes reading the code. Of course, a much better candidate for reading (and testing the scripts would be someone who is knowledgeable about OpenSSH. I'm simply a user of it. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED] Sent: Thursday, October 30, 2003 12:11 PM To: [EMAIL PROTECTED] Subject: Testers for new ssh-*-config scripts wanted! Hi, is anybody here willing to give my new ssh-host-config and ssh-user-config shell scripts a thorough test? I tested them by myself but I have this nagging feeling I missed something important. The important changes: - On NT, try to set permissions on files and directories to a useful value. - On NT, try to set ownership on files and directories to a useful value. Only in ssh-host-config: - Write the /etc/services entries for ssh now with CRLF lineendings. - Remove the code to accomplish old style installations, with old being older than roughly 3 years. - /etc/ssh_config and /etc/sshd_config are not hardcoded here-scripts in the ssh-host-config script anymore, but they are copied and modified from ssh_config and sshd_config files in /etc/defaults/etc. This allows to accomodate changes in the vanilla scripts without having to change the shh-host-config script. - On NT, always set ownership of various files to SYSTEM, if sshd has been installed as service. Both scripts are attached. When testing the new copy config files from /etc/defaults/etc functionality, please think of copying the ssh_config and sshd_config files (if possible the vanilla versions) to /etc/defaults/etc first. Feedback and patches welcome and thanks in advance, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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: Testers for new ssh-*-config scripts wanted!
I have OpenSSH 3.7.1p2-1 installed, but I do not have the 'ssh_config' or 'sshd_config' template files that the 'ssh-host-config' script expects. Am I missing a step here that I should have taken to generate these files? I ran 'cygcheck -f /etc/defaults/etc/ssh_config' and searched the Cygwin Package List at http://cygwin.com/packages, but both searches did not find any packages that should contain these template files. -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED] Sent: Thursday, October 30, 2003 12:11 PM To: [EMAIL PROTECTED] Subject: Testers for new ssh-*-config scripts wanted! Hi, is anybody here willing to give my new ssh-host-config and ssh-user-config shell scripts a thorough test? I tested them by myself but I have this nagging feeling I missed something important. The important changes: - On NT, try to set permissions on files and directories to a useful value. - On NT, try to set ownership on files and directories to a useful value. Only in ssh-host-config: - Write the /etc/services entries for ssh now with CRLF lineendings. - Remove the code to accomplish old style installations, with old being older than roughly 3 years. - /etc/ssh_config and /etc/sshd_config are not hardcoded here-scripts in the ssh-host-config script anymore, but they are copied and modified from ssh_config and sshd_config files in /etc/defaults/etc. This allows to accomodate changes in the vanilla scripts without having to change the shh-host-config script. - On NT, always set ownership of various files to SYSTEM, if sshd has been installed as service. Both scripts are attached. When testing the new copy config files from /etc/defaults/etc functionality, please think of copying the ssh_config and sshd_config files (if possible the vanilla versions) to /etc/defaults/etc first. Feedback and patches welcome and thanks in advance, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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/
