X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Omi4m6LPf+90/bVNLV90z+8inRSSZzDlcXjCW/3oG5Y
	g9lDNl8mDum5PsiF6JherBFZZazy9P6tTnihEmKzJ/lPTtc6eGUsZclW9uXmpRIU
	akbdtF/3y70R1jRoUq8C5OVpljLU3JSOvKNVcdolHWCscz4Yt4GJn4F3GEpWPbWU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=dtJrtM7qLF882HA7bLf3/df+rGw=; b=A0nGTovW4hINsDUUK
	9L1yRAfBt43dOloQWQP5JZayzcP4PMAZe0omAnti+65/3RxGfIiUNKd3gxHI61QM
	pDR5ztGfHQpsfSipuYXQEugoVxVXDDlPKGWnbeu/HnvoEujs30gu+KWW0H1FU1dK
	VuPScls33vvELQM+ofyCWY72SY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=3.4 required=5.0 tests=AWL,BAYES_50,RCVD_IN_PBL,RCVD_IN_SEMBLACK autolearn=no version=3.3.2
X-HELO: konqorde.nl
Message-ID: <52408FA5.8010206@mailme.ath.cx>
Date: Mon, 23 Sep 2013 20:59:49 +0200
From: bartels <bartels AT mailme DOT ath DOT cx>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130704 Icedove/17.0.7
MIME-Version: 1.0
To: Andrey Repin <cygwin AT cygwin DOT com>
Subject: Re: Confused about several issues with setting up cron
References: <B8D164BED956C5439875951895CB4B2211449DC8 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <523F133D DOT 2060806 AT mailme DOT ath DOT cx> <523F4855 DOT 50002 AT mailme DOT ath DOT cx> <42077778 DOT 20130923184405 AT mtu-net DOT ru> <52406732 DOT 8050908 AT mailme DOT ath DOT cx> <711188820 DOT 20130923220835 AT mtu-net DOT ru>
In-Reply-To: <711188820.20130923220835@mtu-net.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 09/23/2013 08:08 PM, Andrey Repin wrote:
> Greetings, bartels!
>
>>>> By the way: SYSTEM is not a user.
>>> Since when?
>> Since Bill Gates stopped sleeping in his garage? :)
>> $ passwd SYSTEM
>> passwd: unknown user SYSTEM
>> Without knowing too much about Windows internals, I have always considered
>> SYSTEM to be a context, rather than a user.
> Your assumption is wrong.
You are persuing a childish argument in semantics.
I think we both know what the SYSTEM means.

And windows loudly disagrees with you:

   $ net user SYSTEM
   The user name could not be found.

> Greatly simplifying, NT AUTHORITY\SYSTEM is a
> built-in access control group, under which whole system kernel works.

You are saying it: SYSTEM is a UAC.

Besides, your argument is off topic, as this thread is about setting up sshd.
cron-config does not accept SYSTEM as a user

Of course we both know that to be just a limitation of cron-config.

- bartels


--
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