X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_00,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26632004.post@talk.nabble.com> Date: Thu, 3 Dec 2009 11:48:56 -0800 (PST) From: Almo To: cygwin AT cygwin DOT com Subject: /bin/kill -f has broken MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 A couple days ago I started working on getting a Windows Scheduled Task going under cygwin. On that day, I tried to fix the "Your group is mkpasswd" problem. I failed. Not sure if this is relevant. Also on that day, /bin/kill -f stopped working. It says "kill: couldn't open pid " I'm wondering if I've somehow changed a permission thing somewhere that causes this not to work. It's been working for at least month before I started messing around a few days ago. Today, I got the mkpasswd problem fixed by doing mkpasswd -u -d ubisoft.org >> /etc/passwd But the kill thing is still broken. Any ideas on what I might have done to break this would be appreciated. -- View this message in context: http://old.nabble.com/-bin-kill--f-%3CwinPID%3E-has-broken-tp26632004p26632004.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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