Hi all,
This is standart output for my man:
man: can't remove /tmp/zmanEfHp6d: No such file or directory
I try to fix it, checked the /tmp directory for exists and have "sticky" bit
set, and found /etc/cron.weekly/man-db don't finished corretly last time.
this is my /etc/cron.wekly/man-db:
#!/
On Sat, Jul 08, 2000 at 01:51:13AM +0200, Philipp Schulte wrote:
> Hello,
> if I try to load a man page that does not exist I do not get the usual
> "No manuel entry for XXX" but this:
>
> nepomuk:~# man foo
> man: warning: /usr/share/man/man1/cvsconfig.1.gz: whatis parse for
> cvsconfig(1)
> fail
Hello,
if I try to load a man page that does not exist I do not get the usual
"No manuel entry for XXX" but this:
nepomuk:~# man foo
man: warning: /usr/share/man/man1/cvsconfig.1.gz: whatis parse for
cvsconfig(1)
failed
Terminated
What's going in here? And what has CVS to do with it?
Thanks,
Phil
Geoffrey L. Brimhall wrote:
>
> Try, as root, executing
>
> mandb
>
> This should hopefully update your man database.
>
> Though I have to admit, I'm having problems with the whatis feature, and I'm
> trying to figure out when it stopped working - when I updated to the latest
> slink or kde. Di
Try, as root, executing
mandb
This should hopefully update your man database.
Though I have to admit, I'm having problems with the whatis feature, and I'm
trying to figure out when it stopped working - when I updated to the latest
slink or kde. Did your man problems happen after a upgrade ?
On
Man I try to update my man pages cache I get the following
error message:
[~] $ man -u bash
Updating index cache for path `/usr/man'. Wait...man: can't open
/usr/man/man1/gnuserv.1: No such file or directory
man: warning: /usr/man/man1/gnudoit.xemacs20.1.gz: bad symlink or
ROFF `.so' request
ma
Are you using bash as your shell and have 'set -a' in /etc/profile or in any
of your bash startup files? If so, try removing 'set -a' or running man under
some other shell.
Bash hanging with man when 'set -a' was in use was reported as bug #8390
during last summer.
// Heikki
--
Heikki Vatiain
>
> Dear Fellow Debian Users:
>
> (let me know if I've posted this to the wrong place; I don't think
> it's a Debian bug per-se, but a local installation problem I can't
> solve).
>
> I'm running Debian-1.3 on two machines, my home computer and my
> work computer. My home computer runs man just
Dear Fellow Debian Users:
(let me know if I've posted this to the wrong place; I don't think
it's a Debian bug per-se, but a local installation problem I can't
solve).
I'm running Debian-1.3 on two machines, my home computer and my
work computer. My home computer runs man just fine, but on my
w
Sorry for the line wraps, but I get this when I try to look
at a man page. And catman just sits there and does nothing!
Anybody?
# man man
man: command exited with status -1: /bin/gzip -dc
'/var/catman/cat1/man.1.gz' |
{ export MAN_PN LESS; MAN_PN='man(1)';
LESS="$LESS\$-Pm\:\$ix8mPm Manual pag
10 matches
Mail list logo
