X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B844C55.1080709@cygwin.com>
References: <3a8528891002220612q63d1ee8fxc69140f9b41685c5 AT mail DOT gmail DOT com> 	 <20100223131352 DOT GA4172 AT tishler DOT net> 	 <3a8528891002230733x644a3bc1na91ddccacafb2e41 AT mail DOT gmail DOT com> 	 <20100223164927 DOT GA212 AT mimosa DOT garydjones DOT name> 	 <20100223182852 DOT GD4172 AT tishler DOT net> 	 <3a8528891002231114p3b23ef4cjced067a0b16fa9fd AT mail DOT gmail DOT com> 	 <20100223193543 DOT GE4172 AT tishler DOT net> 	 <3a8528891002231220w428ec33x74a19275e8a537bf AT mail DOT gmail DOT com> 	 <3a8528891002231237u633942cfyb19ce8ead56d9d1f AT mail DOT gmail DOT com> 	 <4B844C55 DOT 1080709 AT cygwin DOT com>
Date: Tue, 23 Feb 2010 21:56:15 -0500
Message-ID: <3a8528891002231856o2742f5cdx7a67f039a894e520@mail.gmail.com>
Subject: Re: Fetchmail call to procmail no longer works under Cygwin 1.7.1-1
From: Thomas Baker <thomasbaker49 AT googlemail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Tue, Feb 23, 2010 at 4:44 PM, Larry Hall (Cygwin)
<reply-to-list-only-lh AT cygwin DOT com> wrote:
>>> Evidently if it does not find /home/TBaker/.procmailrc, it does
>>> not go looking for /home/tbaker/.procmailrc. =C2=A0Since my entire
>>> file system is based on tbaker, I'd love to find a way to eradicate
>>> the "TBaker" from my system entirely. =C2=A0The guy who set up my XP
>>> installation many years ago set my login as "TBaker" but it has
>>> never caused any practical problems until now.
>
> He should still be shot. ;-)

Maybe along with the IBM guy who swapped Ctrl with CapsLock :-)

> Yeah, I wouldn't go that far when a symbolic link to /home/tbaker would
> suffice.

Yes indeed!
	$ cd /home
	$ mv TBaker TBaker.bak
	$ ln -s /home/tbaker TBaker

Now everything works fine again! :-)

>> It would be nicer to expunge any references to "TBaker" entirely.
>> I guess they are in the Win32 registry? =C2=A0I do not find any in my
>> cygwin configuration files.

I guess that's unnecessary now...

> <http://cygwin.com/cygwin-ug-net/ov-new1.7.html>

Yes, I had indeed scanned through that bulletin but didn't
see this one coming, if it was indeed a "1.7 update" issue
at all.  I guess the issues around the "missing" APLs (see above):

	group:root:rwx
	group:SYSTEM:rwx

turned out to be irrelevant?

> Changing the user name in '/etc/passwd' to use the proper case should
> resolve the problem though.

	$ vim /etc/passwd

has apparently fixed everything.  Much easier than migrating
my whole system from XP to Windows 7.

Thank you, all, for your patience and attention to detail! :-)

Tom

--=20
Tom Baker

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