Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Mon, 4 Jul 2005 11:35:27 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: FischRon DOT external AT infineon DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: man.conf missing after cygwin upgrade
In-Reply-To: <25F7D2213F14794A8767B88203EA2BC9240C7B@mucse201.eu.infineon.com>
Message-ID: <Pine.GSO.4.61.0507041114220.12049@slinky.cs.nyu.edu>
References: <25F7D2213F14794A8767B88203EA2BC9240C7B AT mucse201 DOT eu DOT infineon DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine DOT GSO DOT 4 DOT 61 DOT 0507041114222 DOT 12049 AT slinky DOT cs DOT nyu DOT edu>

On Mon, 4 Jul 2005, FischRon.external wrote:

> After upgrading cygwin to the most recent version, I found that man
> pages aren't displayed anymore; for example
>
>   $ man man
>   Warning: cannot open configuration file /usr/share/misc/man.conf

That's not good...

> Then I saw that my MANPATH looks strange:
>
>   $ echo MANPATH
>   :/usr/ssl/man
>
> Note the leading column, which looks as if some part of the MANPATH has
> been cut off.

...but has nothing to do with this.  The leading colon is valid, and means
to take whatever the current man configuration says the MANPATH should be,
and *append* the content of the MANPATH variable.

> I fixed this by manually adjusting the MANPATH:
>
>   $ export MANPATH=/usr/man:/usr/share/man:/usr/ssl/man
>   $ man man
>
> Now it does display the man-page, but before this it also writes the
> aforementioned error message.

Sure it would.  You're missing a config file, and man can't forgive that.

> Next I did
>
>   $ /usr/sbin/makewhatis
>   $ man -k shell
>
> Now I get that error message *twice* (but then man -k displays an
> overview of the available shell commands, as expected). Now I checked
> /usr/share/misc and found that it has permissions 000. I chmod the
> permissions to 0777. Also I found that /usr/share/misc is empty, i.e.
> there is no file man.conf in it.

Ah, that could be the reason -- permissions 000 would make the postinstall
script fail when copying the man.conf file from its default location.  If
you haven't run setup since upgrading man, see if /var/log/setup.log.full
has any messages from /etc/postinstall/man.sh.

> I checked the man-page for man.conf, but there was no hint how this file
> usually is generated.

You should re-run /etc/postinstall/man.sh.done (or reinstall the man
package) to recreate man.conf.  This is a Cygwin-specific recipe, BTW.

> Of course I can live with this bug, since man eventually seems to do its
> job. Still I'm curious what is going wrong here. Any ideas?

Now that your /usr/share/misc has better permissions, future man upgrades
should work.  If I were you, I'd investigate *why* /usr/share/misc ended
up with 000 permissions in the first place (it's created by setup.exe
using the inherited Windows permissions -- are the ACLs on / too strict?).
What happened with man may happen much less obviously with other packages.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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