weird $MANPATH behavior

weird $MANPATH behavior

Post by John Gibs » Sun, 06 Nov 1994 01:47:08



Why doesn't man pay attention to $MANPATH? Here's what happens when
I try to access a man page that's in my man path. Note that it works
when I specify the path using -M. I'm running the bash shell.

phil$ echo $MANPATH
/usr/lang/man:/usr/man:/usr/local/man:/home/gibson/man
phil$ ls /usr/local/man/man1/mtools.1
/usr/local/man/man1/mtools.1
phil$ man mtools
No manual entry for mtools.
phil$ man -M /usr/local/man mtools

MTOOLS(1)                USER COMMANDS                  MTOOLS(1)

NAME
     Mtools - a collection of tools for manipulating MSDOS files

....

Now, I've just installed mtools, and I've put the man page in
/usr/local/man. Do I need to run some sort of "make" to enter
the man page into a man database?

John

--

111 Thurston Hall                              
Theoretical and Applied Mechanics               phone (607) 255-4077
Cornell Technician Factory, Ithaca NY 14853     fax   (607) 255-2011

 
 
 

weird $MANPATH behavior

Post by Tony Nugen » Sun, 06 Nov 1994 18:42:34



>Why doesn't man pay attention to $MANPATH? Here's what happens when
>I try to access a man page that's in my man path. Note that it works
>when I specify the path using -M. I'm running the bash shell.

[...]

Quote:>Now, I've just installed mtools, and I've put the man page in
>/usr/local/man. Do I need to run some sort of "make" to enter
>the man page into a man database?

Try using catman, I think with the -w option if you don't want
the /cat? directories and files created.  man catman will tell
you what to do.  It updates the windex file, which I think is
what you also need to do.

However, it should still find the man page in /ust/local/man/man1
(or whatever) as long as mtools.1 is in that directory.  (The
extension on the man page must match the ending of the name of
the man subdir that it's in).

Hope this helps.

Cheers
Tony
                                                             \\|//
                                                             (O-O)
  -------------------------------------------------------oOO--(_)--OOo-----
     Tony Nugent  Griffith University, Brisbane, Queensland, Australia

  -------------------------------------------------------------------------

 
 
 

weird $MANPATH behavior

Post by Choe Won G » Thu, 10 Nov 1994 01:49:25


: Why doesn't man pay attention to $MANPATH? Here's what happens when
: I try to access a man page that's in my man path. Note that it works
: when I specify the path using -M. I'm running the bash shell.

: (deleted)

How about running /usr/lib/makewhatis ? (Need to be root..)

 % /usr/lib/makewhatis /usr/local/man

It creates windex at the directory, and man correctly works, for my case.

                                          Won Gyu Choe

+-------------------------------+------------------------------------------+

+-------------------------------+------------------------------------------+
|    Nonlinear and Complex Systems Laboratory,                             |
|    Department of Physics,                                                |
|    Pohang University of Science and Technology.                          |
+--------------------------------------------------------------------------+
|    Sci. Bldg. 3 - 317A,    (Tel) 0562-279-5842    (FAX)  82-562-279-3099 |
+--------------------------------------------------------------------------+

 
 
 

1. : Weird ">" redirect behavior vs. ">>" redirect behavior

Hopefully, someone has already seen this and knows whats up.

Simple script myscript.sh:

#!/bin/sh
i=1

date
while [ 1 ]; do
   echo "Count - ${i}"
   cat /etc/system
   i=`expr ${i} + 1`
   sleep 5
done

Run it as:

nohup sh myscript.sh > /tmp/myscript.log &

Let it run for a while.  Then run:

grep Count /tmp/myscript.log | wc -l
ls -l /tmp/myscript.log
cat /dev/null /tmp/myscript.log
ls -l /tmp/myscript.log
ls -l /tmp/myscript.log
ls -l /tmp/myscript.log
grep Count /tmp/myscript.log | wc -l

The file size info on my system (Solaris 8) for the /tmp/myscript.log
is zero at first and then goes right back to where it was but a bit
more when the next iteration of the cat command output /etc/system.

Also, the first grep..wc -l command shows how many times the script
has basically looped.  The second grep will show only a couple.  This
shows that the inode is saying the file contains everything is always
did but the grep command is saying it only contains up to some of
point a buffer - maybe the output file descriptor buffer?  I'm
guessing I'm not a programmer

If you change the ">" to a ">>" with your nohup , it works as
expected. The file is zeroed out and the inode info shows it growing
as you would expect it to.

What's the differences between ">" and ">>" that makes this happen?
Running the script with ksh does the same thing.

Looks like a bug to me.

--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill

2. lode runner mailing list

3. Weird Ping, weird FTP, weird Telnet... HELP!!!

4. Linux Kernel 2.2.2

5. Weird, weird, weird issue ....

6. HP-UX DTC problems

7. Weird startx behavior

8. Sol8EA, IPSec w/ ESP, anyone functional?

9. Weird behavior during Sol7 install

10. Weird read/write behaviour

11. Please help with weird FTP behavior through browser

12. weird kdm/keyboard behavior on boot, SuSE 8.0

13. WEIRD BEHAVIOR OF LOGIN