X-Spam-Check-By: sourceware.org Message-ID: <44C03C01.8070700@hotmail.com.INVALID> Date: Fri, 21 Jul 2006 12:29:21 +1000 From: Shaddy Baddah Reply-To: cygwin AT cygwin DOT com User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin services using uid 400, not SYSTEM. Why? References: <4460B3A7 DOT 8020201 AT cygwin DOT com> <447F175B DOT 8020505 AT hotmail DOT com> <44BE35F4 DOT 7080900 AT hotmail DOT com DOT INVALID> <44BE3756 DOT 4060509 AT hotmail DOT com DOT INVALID> <44BE501D DOT 30209 AT hotmail DOT com DOT INVALID> In-Reply-To: <44BE501D.30209@hotmail.com.INVALID> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi again, On 7/20/2006 1:30 AM, Shaddy Baddah wrote: > I'm so sorry I didn't pick up on this earlier. Thanks for your > attention. If you have any ideas on the UID 400 problem, I'd still be > very interested to hear what was happening on that. One last bit of diagnosis. In my earlier email, I claimed that the displaying of UID 400 instead of SYSTEM was solved after running cygserver-config. Well, I got a little muddled. I finally got back to the original system that I experienced the problem on (now perhaps not really so much a problem as I thought. I'll elaborate). The attachment is a log of commands that I executed that highlights the problem very clearly. You will see that after running *exim-config* (not cygserver-config), the Cygwin services correctly display as uid SYSTEM, and not 400. Looking at the exim-config script, I am totally bewildered how this could have had any effect on the problem. It looks quite tame (in terms of editing rights, etc...). Perhaps someone might have better insight into this. I am now also not so sure that the processes showing UID 400 was really a problem in the first place. In my earlier email, inetd was not working because of an unrelated problem. I am actually trying to reproduce the problem now, and just ascertain if there was a *rights* problem associated, as it did very much appear to me to be earlier. Regards, Shaddy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/