Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@sourceware.cygnus.com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin@sourceware.cygnus.com>
List-Help: <mailto:cygwin-help@sourceware.cygnus.com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Thu, 19 Aug 1999 12:35:59 -0400
To: Suhaib Siddiqi <ssiddiqi@ipass.net>
Cc: "Cygwin@Sourceware. Cygnus. Com" <cygwin@sourceware.cygnus.com>
Subject: Re: FW: Description of the new 'ntsec' feature
Message-ID: <19990819123559.B11216@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: Suhaib Siddiqi <ssiddiqi@ipass.net>,
	"Cygwin@Sourceware. Cygnus. Com" <cygwin@sourceware.cygnus.com>
References: <19990819000442.B9980@cygnus.com> <NDBBLHPPKKBKPBLLMFJBGENICBAA.ssiddiqi@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <NDBBLHPPKKBKPBLLMFJBGENICBAA.ssiddiqi@ipass.net>; from Suhaib Siddiqi on Thu, Aug 19, 1999 at 06:55:13AM -0400

On Thu, Aug 19, 1999 at 06:55:13AM -0400, Suhaib Siddiqi wrote:
>
>
>> The philosophy was that we could get real ownership and real executable
>> bits and real UNIX permissions.  I also thought it would be nice to have
>> a multi-user NT system where people couldn't routinely kill each others'
>> processes.  I asked Corinna for this and she spent a lot of time on it.
>>
>
>Thanks, I understand now :-)
>
>> I can understand why you don't want to use it.  Just turn if off.
>
>I had it turnedd off.  However the proc_info_signal 1000 kill still kep
>poping up, though not as often as it used to before (til July's last week
>snapshots).  Mostly I see this message (proc_info_signal 1000)
>when MAKE finishes compilation job.

You're going to have to provide an actual error message, Suhaib.
The string proc_info_signal does not show up anywhere in cygwin.

There is a proc_info structure and a sig_send function.  The sig_send
function could emit errors in some situations.  This is probably what
you're seeing and is probably what we need to track down.

cgf

>>If you still are having problems then they're probably not due to
>>ntsec.  There's probably a bug in cygwin from something *I've* done.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

