This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: what's left for 1.5.0
On Mon, Jun 09, 2003 at 09:17:44AM -0400, Jason Tishler wrote:
>On Sun, Jun 08, 2003 at 09:38:14PM -0400, Christopher Faylor wrote:
>> On Sun, Jun 08, 2003 at 09:35:00PM -0400, Jason Tishler wrote:
>> >On Sun, Jun 08, 2003 at 09:13:47PM -0400, Christopher Faylor wrote:
>> >> Anything outstanding or should I release a 1.5.0 test kernel?
>> >
>> >Can we address the following:
>> >
>> > http://cygwin.com/ml/cygwin-developers/2003-06/msg00001.html
>> >
>> >before 1.5.0?
>>
>> Oh yeah, that. I had that sitting in my inbox, too.
>>
>> My feeling is that this is very long standing cygwin behavior so
>> I'm not entirely comfortable just nuking it.
>
>Me too, but IMO something needs to be done. FWIW, this "very long
>standing cygwin behavior" was changed from SIGHUP to SIGINT in the
>following:
>
> 2001-07-25 Kazuhiro Fujieda <fujieda@jaist.ac.jp>
>
> * exception.cc (ctrl_c_handler): Send SIGTERM to myself when
> catch CTRL_SHUTDOWN_EVENT.
SIGINT? I don't see a SIGINT. Are you saying that sending SIGHUP would
be better?
Anyway, it sounds like we need to hear from Kazuhiro Fujieda.
>> Who knows what is relying on it?
>
>I share the above concern too. However, only services can rely on this
>behavior. Additionally, it is likely only services that have been
>ported to be true NT services (i.e., do not run under cygrunsrv) could
>be affected. The set of such services is most likely very small --
>possibly only containing inetd.
It's possible to run any raw cygwin app as a service, right?
cgf