delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/02/23/15:21:08

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20100223193543.GE4172@tishler.net>
References: <3a8528891002220612q63d1ee8fxc69140f9b41685c5 AT mail DOT gmail DOT com> <3a8528891002221452h48008b49t2a17aa42a97ee5e AT mail DOT gmail DOT com> <20100223021729 DOT GA6116 AT tishler DOT net> <3a8528891002221948k38c0cc7ei24a4822a86803df6 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>
Date: Tue, 23 Feb 2010 15:20:46 -0500
Message-ID: <3a8528891002231220w428ec33x74a19275e8a537bf@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
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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 2:35 PM, Jason Tishler wrote:
>> > What does the following indicate?
>> >
>> > ?? ??$ procmail VERBOSE=3Don <msg.mbox
>>
>> procmail: [4092] Tue Feb 23 14:11:50 2010
>> procmail: Locking "/var/spool/mail/TBaker.lock"
>> [snip]
>
> You should have seen a line like the following:
>
> =C2=A0 =C2=A0procmail: Rcfile: "/home/TBaker/.procmailrc"
>
> between the above two lines. =C2=A0For some reason, procmail is not findi=
ng
> your $HOME/.procmailrc file.

This is what I find...:

	$ cd /home
	$ ls
	Administrator TBaker tbaker
	$ find TBaker
	TBaker
	TBaker/.bashrc
	TBaker/.bash_history
	TBaker/.bash_profile
	TBaker/.inputrc
        $

In other words, all of my files are in /home/tbaker except for the new
bash configuration
files, which are (the only) files in /home/TBaker.

When I upgraded to Cygwin 1.7, I now vaguely recall seeing
a message about creating new .bashrc files when I first ran the shell.

If I rename 'TBaker' to 'foobar' (to take it out of action) and re-run...:

	$ procmail VERBOSE=3Don <test.mbox
        procmail: [3240] Tue Feb 23 14:59:34 2010
        procmail: Locking "/var/spool/mail/TBaker.lock"
        procmail: Assigning "LASTFOLDER=3D/var/spool/mail/TBaker"
        procmail: Opening "/var/spool/mail/TBaker"
        procmail: Acquiring kernel-lock
        procmail: Unlocking "/var/spool/mail/TBaker.lock"
        procmail: Notified comsat: "TBaker AT 22513:/var/spool/mail/TBaker"
        From tbaker AT tbaker DOT de Sat Feb 20 16:47:32 2010
         Subject: TEST TEST TEST TEST TEST TEST TEST TEST TEST
        Folder: /var/spool/mail/TBaker                   542

Evidently if it does not find /home/TBaker/.procmailrc, it does
not go looking for /home/tbaker/.procmailrc.  Since my entire
file system is based on tbaker, I'd love to find a way to eradicate
the "TBaker" from my system entirely.  The 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.

Tom

--=20
Tom Baker <tbaker AT tbaker DOT de>

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019