-u didn't work.
Gave a whole bunch of messages. But when I used the -u option on a
manual that was good, I got the same messages.
BTW, I had to write some code to do this, but is there a native way to
do, in effect a "dir rpm.* /s" ?
When I use the -R option with LS, it doesn't seem to like the
specification of a file name or generic name.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 05/27 2:02 PM >>>
Perhaps: -u??
>From man --help:
usage: man [-c|-f|-k|-w|-tZT device] [-adlhu7V] [-Mpath] [-Ppager]
[-Slist]
[-msystem] [-pstring] [-Llocale] [-eextension] [section]
page
...
-a, --all find all matching manual pages.
-d, --debug emit debugging messages.
-e, --extension limit search to extension type
`extension'.
-f, --whatis equivalent to whatis.
-k, --apropos equivalent to apropos.
-w, --where, --location print physical location of man page(s).
-l, --local-file interpret `page' argument(s) as local
filename(s).
-u, --update force a cache consistency check.
-r, --prompt string provide the `less' pager with a prompt
-c, --catman used by catman to reformat out of date cat
pages.
-7, --ascii display ASCII translation of certain
latin1
chars.
-t, --troff use groff to format pages.
-T, --troff-device device use groff with selected device.
-Z, --ditroff use groff and force it to produce ditroff.
-X, --gxditview use groff and display through gditview
(X11):
-X = -TX75, -X100 = -TX100, -X100-12 =
-TX100-12.
-D, --default reset all options to their default values.
-M, --manpath path set search path for manual pages to
`path'.
-P, --pager pager use program `pager' to display output.
-S, --sections list use colon separated section list.
-m, --systems system search for man pages from other unix
system(s).
-L, --locale locale define the locale for this particular man
search.
-p, --preprocessor string string indicates which preprocessors to
run.
e - [n]eqn p - pic t - tbl
g - grap r - refer v - vgrind
-V, --version show version.
-h, --help show this usage message.
Tom Duerbusch
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
iscity.com> cc:
Sent by: Linux on Subject: [LINUX-390]
Man formatting problem
390 Port
<[EMAIL PROTECTED]
IST.EDU>
05/27/2003 12:59
PM
Please respond to
Linux on 390 Port
I shot my self in the foot....again.
I'm bringing up Suse 8 with the default installion. The manuals kept
referring to installing with a minimum of 256 MB or 560 MBs. But now
that I had a system up, I started bring down the size to see how small
it can be and still run.
In all cases, I was running without a swap file.
I could boot the system at 16 MBs and it would come up fine (12 MBs
wouldn't boot). So I logged on and tried some commands.
"top" worked fine
"man top" worked fine
"man rpm" failed
It seems that the first time you issue a "man" for a particular topic,
extra work, is done and is saved. Subsequent executions, even after
an
IPL, don't experience the "great" use of CPU that is done initially.
However, in 16 MB, "man rpm" failed. And it will now fail even with a
machine size of 256MBs. Apparently, whatever was partically done with
the "rpm" man pages isn't going to get redone. "man rpm" now fails
consistantly.
I have considered reinstalling Suse 8 and just learn not to IPL with
such limited storage.
I have also considered ftp'ng the man page from another Linux 8
machine.
But there must be a better way.
Is there a way to force the "man" command to redo the man page in
question?
"man man" doesn't show any syntax that may do this. Perhaps there is
another command that will?
Perhaps whatever process there is to build a man page would be needed
to
"cold start" this process.
Thanks
Tom Duerbusch
THD Consulting
