Mail Archives: cygwin-developers/2000/07/29/12:39:21
I've made a CVS branch for Cygwin 1.1.4, since it seems that I've screwed
up CYGWIN=binmode stuff. I've fixed this on the CVS trunk and then made
a branch. Or, at least I've pushed the bits around so that the problem is
different...
Why make a branch? Well, I've also checked in my (huge) changes that
almost make cygwin pids == windows pids. I'd like this change to show
up in a few snapshots before it is unleashed on the unsuspecting public.
So, I expect to make a 1.1.4 release next week sometime, followed by a
1.1.5 in a month or so.
In the meantime, I get to play with CVS branch madness. What fun.
If you build a cygwin from the current CVS, you will get 1.1.5. The
most noticeable features of this release are new options to 'ps' and
'kill'.
A standard 'ps' now defaults to what used to be 'ps -l'. This was so
that it was obvious that there are still potentially two different pids
associated with a process, the windows and cygwin pids. A process has
two different pids when it has been execed by a cygwin process, as has
always been the case. 'ps -s' produces the previous default output.
'ps -W' provides (minimal) information for every process on your system,
not just cygwin processes. You get more info on Windows NT, of course.
This sort of works on Windows 95, but some processes are inexplicably
missing from the display. I don't know why. I really hate... Oops.
I've used up my quota this week...
The 'kill' command takes a '-f' option to force the termination of a
process. This will kill any process with the given pid. I haven't
gotten this working on Windows 95, yet, due to the fact that the pids
are either really large positive values or really small negative values.
Neither seems to work right. Killing using 'cygwin pids' which are
sort of large positive numbers should work ok.
cgf
- Raw text -