I think it's a problem with the way exim is configured.
Exim is mailing the report locally. So that's why we couldn't find
anything about cron-daily, man-db, or file permissions !
I can see the same error on two freshly installed Debian unstable
boxes, with completely diff
| Thanks for your suggestion, i'll report if it worked.
No, sorry, even with /var mounted 'suid' i got still the same error mail...
/etc/cron.daily/man-db:
find: /var/cache/man: Permission denied
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
ough i knew i din't think too much about that 'owner'
implies nosuid.
| First, try mounting /var without the nosuid part.
(How do i trigger a normal cron man-db run ?)
... I'll see tomorrow.
| The way this ought to work (and I thought it did) was for example,
| a hypot
On Fri, 18 Aug 2006 03:16:08 +0200
Micha <[EMAIL PROTECTED]> wrote:
> /etc/cron.daily/man-db:
> find: /var/cache/man: Permission denied
Cron likely runs with no (or low level) permissions.
> /var is mounted as:
> /dev/hda10 on /var type ext2 (rw,nosuid,nodev,errors=remount-
(Please first cc to me, if i got a reply i will switch to reading the archive)
Hello,
This is Debian Sid, and since a few months i got this error
message (sent via local mail):
/etc/cron.daily/man-db:
find: /var/cache/man: Permission denied
and i just can't come up with any explan
On Tue, May 16, 2006 at 12:00:15 +0300, David Baron wrote:
> On Tuesday 16 May 2006 11:48, Florian Kulzer wrote:
> > On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote:
> > > Get a whole series of messages like:
> > > mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF
>
On Tuesday 16 May 2006 11:48, Florian Kulzer wrote:
> On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote:
> > Get a whole series of messages like:
> > mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF
> > `.so' request
> > mandb: can't open /usr/share/man/man1x/xtrap.1
On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote:
> Get a whole series of messages like:
> mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF
> `.so'
> request
> mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory
>
> I tried recreating the d
Get a whole series of messages like:
mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF `.so'
request
mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory
I tried recreating the db, still happens.
How to fix?
--
To UNSUBSCRIBE, email to [EMAIL PROTE
"Edward C. Jones" <[EMAIL PROTECTED]> wrote:
> I use a PC with a AMD Athlon64 3500+ chip and up-to-date Debian unstable
> i386 port.
>
> Each day I get an email from cron that says:
>
> /etc/cron.daily/man-db:
> mandb: can't open /usr/share/man/man1x/x
I use a PC with a AMD Athlon64 3500+ chip and up-to-date Debian unstable
i386 port.
Each day I get an email from cron that says:
/etc/cron.daily/man-db:
mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory
mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad sy
Bob Proulx wrote:
> Kevin B. McCarty wrote:
>>Once a day I get the following email message from the man-db cron job:
>>
>>>/etc/cron.daily/man-db:
>>>mandb: warning: /usr/share/man/man1/x-terminal-emulator.1.gz is a dangling
>>>symlink
>
> It woul
Kevin B. McCarty wrote:
> Please CC replies to me as I'm not subscribed.
> Once a day I get the following email message from the man-db cron job:
> > /etc/cron.daily/man-db:
> > mandb: warning: /usr/share/man/man1/x-terminal-emulator.1.gz is a dangling
> > symlink
David E. Fox wrote:
> On Tue, 13 Sep 2005 09:44:15 -0400
> "Kevin B. McCarty" <[EMAIL PROTECTED]> wrote:
>>>benjo[1]:~% ls -l /usr/share/man/man1/x-terminal-emulator.1.gz
>>>lrwxrwxrwx 1 root root 42 2005-09-09 10:05
>>>/usr/share/man/man1/x-terminal-emulator.1.gz ->
>>>/etc/alternatives/x-term
On Tue, 13 Sep 2005 09:44:15 -0400
"Kevin B. McCarty" <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> Once a day I get the following email message from the man-db cron job:
>
> > /etc/cron.daily/man-db:
> > mandb: warning: /usr/share/man/man1/x-terminal-
Hi list,
Once a day I get the following email message from the man-db cron job:
> /etc/cron.daily/man-db:
> mandb: warning: /usr/share/man/man1/x-terminal-emulator.1.gz is a dangling
> symlink
This in spite of all the evidence:
> benjo[1]:~% ls -l /usr/share/man/man1/x-terminal-e
On Fri, Sep 05, 2003 at 11:31:10AM -0400, [EMAIL PROTECTED] wrote:
> How do I clean this up?
>
> /etc/cron.daily/man-db:
> mandb: warning: /usr/share/man/man3/Judy.3x.bz2 is a dangling symlink
> mandb: warning: /usr/share/man/man3/judy.3x.bz2 is a dangling symlink
> mandb: warni
How do I clean this up?
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man3/Judy.3x.bz2 is a dangling symlink
mandb: warning: /usr/share/man/man3/judy.3x.bz2 is a dangling symlink
mandb: warning: /usr/share/man/man3/Judy1.3x.bz2 is a dangling symlink
mandb: warning: /usr/share/man/man3
0, 2003 at 09:00:11AM -0400, John Covici wrote:
> > Hi. After upgrading to 2.4.1-12 of man-db it seg faults in the
> > cron.daily script at the start-stop-daemon line.
>
> 2.4.1-12, really? I know that there was a problem with the woody
> backport but was not aware of any
On Sun, Aug 10, 2003 at 09:00:11AM -0400, John Covici wrote:
> Hi. After upgrading to 2.4.1-12 of man-db it seg faults in the
> cron.daily script at the start-stop-daemon line.
2.4.1-12, really? I know that there was a problem with the woody
backport but was not aware of anything in unstab
On Sun, Aug 10, 2003 at 03:03:30PM -0400, John covici wrote:
> Well, tell me the steps -- it will be easier that way and I'll get
> the source and rebuild.
As root:
# apt-get install build-essential debhelper flex gettext groff libdb3-dev
As an ordinary user:
$ apt-get source ma
Hi. After upgrading to 2.4.1-12 of man-db it seg faults in the
cron.daily script at the start-stop-daemon line.
I am using kernel 2.4.21 vanilla if it makes any difference.
Thanks.
--
John Covici
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
> looks like an missing entry in /etc/passwd:
> --- /etc/passwd on _my_ system
> man:x:6:100:man:/var/cache/man:/bin/sh
> ---
> May be this entry was accidently deleted, just add it again with your
> favorite editor. Reinstallation of the package schould finish without
> error
> -- gk
Thank yo
nstalling man-db. Can anyone please tell me how to fix this problem:
>
> Fetched 334kB in 1m6s (4997B/s)
> Selecting previously deselected package man-db.
> (Reading database ... 33532 files and directories currently installed.)
> Unpacking man-db (from
Hi everyone.
Error installing man-db. Can anyone please tell me how to fix this problem:
Fetched 334kB in 1m6s (4997B/s)
Selecting previously deselected package man-db.
(Reading database ... 33532 files and directories currently installed.)
Unpacking man-db (from .../man
On Sun, Sep 30, 2001 at 07:30:57AM -0500, Colin Watson wrote:
> On Sat, Sep 29, 2001 at 02:42:33AM +0100, Carlos Sousa wrote:
> > my 'man' apparently runs with root privileges:
> >
> > $ ll /usr/lib/man-db
> > total 220
> > drwxr-xr-x2 root root
On Sat, Sep 29, 2001 at 02:42:33AM +0100, Carlos Sousa wrote:
> Colin Watson wrote:
> > (can't have been any vaguely recent version of man-db, as none of them
> > run with root privileges ...). man-db can certainly work around it,
>
> my 'man' apparently
Colin Watson wrote:
> (can't have been any vaguely recent version of man-db, as none of them
> run with root privileges ...). man-db can certainly work around it,
my 'man' apparently runs with root privileges:
$ ll /usr/lib/man-db
total 220
drwxr-xr-x2 root root
drwxr-sr-x2 man root 4096 Jul 1 04:45 opt
> > You might like to file a bug report against the man-db package, where we
> > can sort this out in more detail.
>
> Is it man-db or is it me? I've been following this list for some time
> now, and I can't
2 root root 4096 Sep 27 23:30 /var/cache/man/cat7/
drwxr-sr-x 2 root root 4096 Sep 27 23:30 /var/cache/man/cat8/
You might like to file a bug report against the man-db package, where we
can sort this out in more detail.
Is it man-db or is it me? I've been following this list for s
On Fri, Sep 28, 2001 at 12:04:19AM +0100, Carlos Sousa wrote:
> On my machine root keeps getting email from cron saying "rm: cannot
> unlink `/var/cache/man/cat8/(whatever).gz': Permission denied".
>
> I've traced this behaviour to the man-db cron job trying t
On my machine root keeps getting email from cron saying "rm: cannot
unlink `/var/cache/man/cat8/(whatever).gz': Permission denied".
I've traced this behaviour to the man-db cron job trying to remove
stale files from the /var/cache/man tree while running as user 'm
on Thu, Sep 27, 2001 at 01:15:03AM +1000, Craig W ([EMAIL PROTECTED]) wrote:
> Hi,
> I am having problems with man-db, could someone please advise on why this is
> happening & any solutions, pointers I can try.
>
> Cron <[EMAIL PROTECTED]> test -e /usr/sbin/anacron ||
On Wed, Sep 26, 2001 at 06:08:17PM +0200, Peter Palmreuther wrote:
> On Wednesday, September 26, 2001 at 5:15:03 PM,
> you wrote (at least in part):
> > I am having problems with man-db, could someone please advise on why this is
> > happening & any solutions, pointers I
Hello Craig,
On Wednesday, September 26, 2001 at 5:15:03 PM,
you wrote (at least in part):
> Hi,
> I am having problems with man-db, could someone please advise on why this is
> happening & any solutions, pointers I can try.
...
> run-parts: /etc/cron.weekly/man-db exited with r
Hi,
I am having problems with man-db, could someone please advise on why this is
happening & any solutions, pointers I can try.
Cron <[EMAIL PROTECTED]> test -e /usr/sbin/anacron || run-parts --report
/etc/cron.weekly
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-I
"Sang-Kyun Kim" <[EMAIL PROTECTED]> wrote:
> "dselect" automatically upgrades man-db.
>
> But, it cannot be configured, display this error messge.
>
>-
>Setting up man-db (2.3.16-1.1) ...
>chown: man.root: invalid user
>dpkg: e
"dselect" automatically upgrades man-db.
But, it cannot be configured, display this error messge.
-
Setting up man-db (2.3.16-1.1) ...
chown: man.root: invalid user
dpkg: error processing man-db (--configure):
subprocess post-installation script returned error e
I did this just a fw days ago. In fact I removed every bad
symlink in each man directory, yet now they are back. It is as if man-db is
doing this to me. can anyone explain what exactly man-db does. Obviously
it compacts my man files. DOes it keep the originals anywhere? Anyone else
have this problem?
I've just installed man-db and manpages from the following URL
http://www.debian.org/Packages/stable/doc/
follow the instructions, then man command IS avaliable with comfort.
Alan Tam.
ayin wrote:
> Dear Sir
>
> When I install the man-db package , the dselect utility tell me t
On: Thu, 15 Oct 1998 16:53:15 +0800 ayin writes:
>
> Dear Sir
> When I install the man-db package , the dselect utility tell me that
> I should have groff. But groff need libg++272.
>
> The problem is that I have installed libg++272( the dselect show
> installed) , but
Dear Sir
When I install the man-db package , the dselect utility tell me that I
should have groff. But groff need libg++272.
The problem is that I have installed libg++272( the dselect show installed)
,
but the groff item still shows that libg++272 does not appear in the
installed packages list
I keep getting this error whenever I try to configure anything through
dselect:
Checking for languages ... de_DECan't locate Getopt/Long.pm in @INC at
/usr/sb
in/chmanconfig line 38.
BEGIN failed--compilation aborted at /usr/sbin/chmanconfig line 38.
dpkg: error processing m
In my old bo man-db package I was able to select the manual pages I
get using the LANG variable. For example, after installing
manpages-de and setting LANG=de_DE I was getting the german version if
available.
In the hamm version of man-db (2.3.10-63) this no longer works. Now
it seems that
unning the script the man -w something worked.
> > > Has someone else experienced this ?
> >
> > Yes. Please refer to the Debian-user faq:
> > http://www.debian.org/cgi-bin/fom?file=58&showEditCmds=1
> >
> > it´s because the database of man-db is corrupted.
&
have perl installed. A bug has already been filed.
>
... a long history ...
I avoid to comment on the request to have a "pure" debian system
(without perl) that made changes into bo (1.3) which can be without perl
installed (previous couldn't).
This bug (which was passed as a "
> > Checking for languages ... de_DECan't locate Getopt/Long.pm in @INC at
> > /usr/sbin/chmanconfig line 38.
> > BEGIN failed--compilation aborted at /usr/sbin/chmanconfig line 38.
> > dpkg: error processing man-db (--install):
> > subprocess post-installatio
alling
> the manpaged.
>
> >>>> positive messages deleleted <<<<
>
> Checking for languages ... de_DECan't locate Getopt/Long.pm in @INC at
> /usr/sbin/chmanconfig line 38.
> BEGIN failed--compilation aborted at /usr/sbin/chmanconfig line 38.
&
Checking for languages ... de_DECan't locate Getopt/Long.pm in @INC at
/usr/sbin/chmanconfig line 38.
BEGIN failed--compilation aborted at /usr/sbin/chmanconfig line 38.
dpkg: error processing man-db (--install):
subprocess post-installation script returned error exit status 2
Thanks,
Nebu
t; > Has someone else experienced this ?
>
> Yes. Please refer to the Debian-user faq:
> http://www.debian.org/cgi-bin/fom?file=58&showEditCmds=1
>
> it´s because the database of man-db is corrupted.
The above reference (fom?...) is claims that the DB is getting corrupted a
e experienced this ?
Yes. Please refer to the Debian-user faq:
http://www.debian.org/cgi-bin/fom?file=58&showEditCmds=1
it´s because the database of man-db is corrupted.
HTH,
Jens
---
[EMAIL PROTECTED] [EMAIL PROTECTED]
Key ID: 2048/E451C639 Jens Ritter
Key fingerprint: 5F 3D 43 1E 24 1E CC
On a previous posting I said that I needed to run the mentioned cron script
manualy.
Now I found out when I had to run this script manualy.
It turned out that it happaned after a shutdown command when I was logged to
an xterm (and su to root). Prior to the shutdown I also had an xman window
open
Hi.
I'm having problems with Motif man pages which I installed on my system.
If I run, say, "man XmString" I get the following error messages:
Reformatting XmString(3x), please wait...
zsoelim: /usr/X11R6/man/man3/XmString.3x:292: \\$1: No such file or
directory
zsoelim: \\$1.gz: No such file or
Andy Spiegl wrote:
>
> This is a little off-topic, but related to man-pages, too.
>
> My problem is that - when running "man -a" as I always do - I often
> get to see man pages multiple times.
Yes, and if you skip one choosing Ctrl-D its entry disappear from the
next run (and from the whatis dat
ig
A trimmed down output of "dpkg -l '*man*'" is here:
pn man (no description available)
un man-aeb (no description available)
un man-browser (no description available)
ii man-db 2.3.10-38 Display the on-l
Joey Hess wrote:
>
> You might want to refer to bug reports #10483, #11278, etc at
> http://www.debian.org/Bugs/db/pa/lman-db.html - the maintainer is
> aware of the problem, and I hope he figures out a fix soon.
>
I have all the reports, but I wasn't able to reproduce the problem in
any way.
I'
[EMAIL PROTECTED] wrote:
> Monthly, or more often, since installing Bo 1.3 on new system, I have had to
> re-install man-db, after getting segmentation faults whenever executing man.
> I don't believe this is related to libc6, as has been reported. It happens
> at almost rando
Monthly, or more often, since installing Bo 1.3 on new system, I have had to
re-install man-db, after getting segmentation faults whenever executing man.
I don't believe this is related to libc6, as has been reported. It happens
at almost random times. Perhaps certain package upgrades
Pann McCuaig <[EMAIL PROTECTED]> writes:
> I've installed 1.3.1 on a small (40MB) partition on my laptop. I did
> the base install, exited immediately from dselect, and have used
> dpkg to install just the packages I feel I need to have a real OS
> available.
>
>
I've installed 1.3.1 on a small (40MB) partition on my laptop. I did the
base install, exited immediately from dselect, and have used dpkg to install
just the packages I feel I need to have a real OS available.
Configuration of man-db fails for lack of Long.pm (which is _not_ on my
s
Thank you, Christian. Yes, man-db's unspecified dependency on perl
appears to be the problem. And so it seems, as BG Lim pointed out
(thank you), that this is a small packaging bug. Thanks, folks.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
T
The problem is that the script needs Long.pm, which (I think), is a Perl
script. Install Perl from interpreters and it should be fine.
I think this is a bug, because perl is big and not many people esp newbies
want it or need it, just to install man, which shoudl be the first thing
any newbie inst
libgdbm1
Suggests: perl-suid, perl-debug
Conflicts: io
and it did succeed installing man-db.
Greetings,
Christian
--
Christian Meder, email: [EMAIL PROTECTED]
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks fo
ar/catman/X11R6/cat5
Checking for languages ... de_DECan't locate Getopt/Long.pm in @INC at
/usr/sbin/chmanconfig line 38.
BEGIN failed--compilation aborted at /usr/sbin/chmanconfig line 38.
dpkg: error processing man-db (--install):
subprocess post-installation script returned err
64 matches
Mail list logo
