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 Date: Tue, 13 Aug 2002 10:00:12 -0400 From: Jason Tishler Subject: Re: Multiple users in fetchmail In-reply-to: <20020812151949.GA2168@tishler.net> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20020813140012.GD2548@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20020811140204 DOT 3f1780c9 DOT jim DOT george AT blueyonder DOT co DOT uk> <20020812103113 DOT H17250 AT cygbert DOT vinschen DOT de> <20020812132847 DOT GB1928 AT tishler DOT net> <20020812153640 DOT R17250 AT cygbert DOT vinschen DOT de> <20020812151949 DOT GA2168 AT tishler DOT net> On Mon, Aug 12, 2002 at 11:19:49AM -0400, Jason Tishler wrote: > Unfortunately, I also have to teach fetchmail that a UID of 18 is > equivalent to 0 (i.e., root) under Cygwin. Without this "ctl->uid" > above is always 18 and *not* the user's real UID. It will take me > some time to track this down... And I hope that the fetchmail > maintainer will accept such a patch... Actually, I needed to teach procmail that 18 is the root UID not fetchmail. As it turned out, procmail already had the following: #define ROOT_uid 0 so the change was trivial: #ifdef __CYGWIN__ #define ROOT_uid 18 #else /* !__CYGWIN__ */ #define ROOT_uid 0 #endif /* __CYGWIN__ */ Nevertheless, I will submit a patch to the fetchmail maintainer to treat a UID of 18 as the root UID under Cygwin. In this way, Cygwin fetchmail running under the LocalSystem account will behave identical to fetchmail running under root on other Unixes. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/