Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 31 May 2005 22:23:49 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.17 regression - 'printer name is invalid' is back
Message-ID: <20050601022348.GK9864@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <429D11E7 DOT 6070201 AT cdvinc DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <429D11E7.6070201@cdvinc.com>
User-Agent: Mutt/1.5.8i

On Tue, May 31, 2005 at 06:39:51PM -0700, Tim Beuman wrote:
>This problem probably is a result of the modifications in 
>src/winsup/cywin/path.cc introduced in version 3.373.
>
>lpr.exe uses cygwin_conv_to_win32_path() which now is forced to check 
>for non-absolute pathnames only:
>
>version 1.373:
>path_conv p (path, PC_SYM_FOLLOW | PC_NO_ACCESS_CHECK | PC_NOFULL);
>
>version 1.372:
>path_conv p (path, PC_SYM_FOLLOW | PC_NO_ACCESS_CHECK);
>
>lpr.exe probably should use cygwin_conv_to_full_win32_path() for a 
>remote printer (and a local printer too?).

Corinna fixed this problem on Saturday but I neglected to produce a new
snapshot.  I'll do that now.

cgf

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