/bin/kill -f has broken

2009-12-03 Thread Almo
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

Re: Problem with bash script running under NT AUTHORITY\SYSTEM

2009-12-03 Thread Almo
Larry Hall (Cygwin) wrote: > > Remember, SYSTEM is not you. It doesn't have your environment or your > access > rights. You need to be very careful and explicit with paths, files, and > their > permissions. Whatever permissions and paths you have in your environment > has > to be replicated

Re: Problem with bash script running under NT AUTHORITY\SYSTEM

2009-12-02 Thread Almo
Dave Korn-6 wrote: > > Almo wrote: > >> echo "/usr/bin/gzip -f ./$1.sql 2>> error.log" >> error.log >> usr/bin/gzip -f ./$1.sql 2>> error.log >> >> The output I get is: >> >> hyperquest_v2.sql >> /usr/bin/gzip

Problem with bash script running under NT AUTHORITY\SYSTEM

2009-12-02 Thread Almo
Hi! I'm using cygwin and this command in a function works when I'm logged in as me: gzip -f ./$1.sql 2>> error.log so it zips hyperquest_v2.sql as the argument I send it is "hyperquest_v2". When this is run from NT AUTHORITY\SYSTEM as a scheduled task, I get an error. So I put in some debug ou