X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4EEC2F93.9090405@bopp.net> Date: Fri, 16 Dec 2011 23:58:43 -0600 From: Jeremy Bopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: I gave up and reverted to 1.5 References: <20111217045507 DOT GQ14806 AT mrvideo DOT vidiot DOT com> In-Reply-To: <20111217045507.GQ14806@mrvideo.vidiot.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 12/16/2011 10:55 PM, Mike Brown wrote: > Long standing programs like cron just install and run. Using cygwin 1.5, > it does. Using 1.7, it does not. I have no idea what was done to 1.7 to cause > cron to not work, no matter what the Hell I try to do. > > So I said f**k it and removed all of the 1.7 files and reinstalled 1.5 from > the local files that I have. Did you ever try to install 1.7 from scratch rather than attempt an upgrade of 1.5? The upgrade /should/ work, but it's also pretty easy to try a fresh installation. You can even do it along side your 1.5 installation so that you can work out the kinks without making your system non-functional. Regarding your cron and sshd issues, the only other thing I can think that would bust them both as you described is the change to user access token management. The details of how things are in 1.7 are here: http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview Basically, things have changed, but I can't really tell you what exactly myself. I can assure you though that while I never had need of cron I did make extensive use of sshd under Cygwin 1.7 on Windows 2000, XP, 2003, 2008, and 7 systems. It worked well for virgin systems, but I may have had to clobber the accounts used for sshd services and re-run ssh-host-config on systems where I upgraded from Cygwin 1.5. That was some time ago now, so I can't remember for sure. If in doubt, start everything on a virgin system to prove that you can get things working. Then compare with the upgraded system to figure out the differences. Of course, if there's no compelling need to upgrade to Cygwin 1.7, skip it and have some fun in your life. ;-) -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple