I have also had problems with man pages on FC2.  I can't say for sure
that they worked before I put oscar in though.


On Wed, 23 Feb 2005 15:08:50 -0800, Bernard Li <[EMAIL PROTECTED]> wrote:
> Hey Thomas:
> 
> > [Slow SSH]
> >    I've experience an issue with a user of PVM, that
> > ultimately turned out
> >    to be a default SSH configuration issue.  (We ssh for PVM_RSH.) The
> >    problem was that ssh was *very* slow b/c Xauth was
> > failing.  If you did
> >    an 'ssh -x' to disable Xforwarding at the client level things were
> >    faster.
> >
> >    To cut to the chase, I modified the user's
> > /etc/ssh/ssh_config so that
> >    the client on the headnode didn't try to setup
> > X11Forwarding by default.
> >    However, I'm not sure why this was happening or if this
> > was particular to
> >    this user...but it sure was a problem and if others are
> > having it we need
> >    to fix in in v4.1.
> 
> When I ssh as root from the headnode to a newly imaged node, here's what
> I get:
> 
> Warning: No xauth data; using fake authentication data for X11
> forwarding.
> /usr/X11R6/bin/xauth:  creating new authority file /root/.Xauthority
> 
> I think the xauth error message has constantly caused us grief - I would
> be in favour of fixing this for 4.1.
> 
> >
> > [MANPATH]
> >    The MANPATH bug seems to still be around.  This is the
> > problem where
> >    stock manual pages are not available b/c we define MANPATH
> > but don't
> >    leave the "::" (search the system areas too).  The manual
> > fix is easy,
> >           export MANPATH=$MANPATH:
> >
> >    The correct fix (which I thought was in but maybe it is
> > not) is to have
> >    switcher/modules insert this "default" manpath search item
> > at the end (or
> >    beginning) after (before) all the OSCAR modules are loaded.
> 
> I suggest that we up this bug to priority 9 such that we can have it
> looked at and fixed.  It is pretty bad that on a newly installed
> cluster, you can't do something like man man ;-)
> 
> > I think that at sometime in the future when we have
> > sufficient documentation on how to write an APItest (i'm
> > working on getting this), we should have new tests written
> > for known bug fixes to make sure they don't crop back up...or
> > that they're genuinely fixed.  They wouldn't have to run via
> > test_cluster or the GUI but could be run manually by a
> > developer or for diagnostics by a user.
> 
> This is a good idea - we should put it down on the map :)
> 
> Cheers,
> 
> Bernard
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id396&opclick
> _______________________________________________
> Oscar-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to