El Fri, 12 Dec 2014 20:56:00 +0100, José Miguel (sio2) escribió:
El Fri, 12 de Dec de 2014, a las 06:05:35PM +, Camaleón dijo:
No es una estupidez siempre y cuando lo hagas como prueba para
comprobar si el raid 1 funciona como debe o no.
Lo que ya no me parece tan normal es que lo
montado el sistema raíz en modo
sólo lectura. Mirando cuál era el culpable he visto el error se produce
al instalar man-db, incluso aunque decida actualizar sólo man-db:
#v+
# aptitude install man-db
[...]
(Leyendo la base de datos ... 32148 ficheros o directorios instalados
actualmente
produce
al instalar man-db, incluso aunque decida actualizar sólo man-db:
(...)
Y luego se siguen escupiendo muchos errores producidos porque el sistema
raíz se ha puesto en sólo lectura. He intentado unas cuantas veces la
operación a partir de la jessie sin actualizar y siempre ocurre lo
mismo
El Fri, 12 de Dec de 2014, a las 05:19:40PM +, Camaleón dijo:
Yo interpreto lo siguiente: se te ha caído el raid 1 (por el motivo que
sea, primer problema a analizar, es decir, comprobar si realmente el raid
está caído o se debe a su estado forzado a un sólo disco ¿?)
Hay una
El Fri, 12 Dec 2014 18:47:25 +0100, José Miguel (sio2) escribió:
El Fri, 12 de Dec de 2014, a las 05:19:40PM +, Camaleón dijo:
Yo interpreto lo siguiente: se te ha caído el raid 1 (por el motivo que
sea, primer problema a analizar, es decir, comprobar si realmente el
raid está caído o
El Fri, 12 de Dec de 2014, a las 06:05:35PM +, Camaleón dijo:
No es una estupidez siempre y cuando lo hagas como prueba para comprobar
si el raid 1 funciona como debe o no.
Lo que ya no me parece tan normal es que lo tengas de manera constante
roto (con un sólo disco), ya que de esa
Le 24 janvier 2009 02:40, Thomas Preud'homme
thomas.preudho...@celest.fr a écrit :
Alors moi je suis pas contrariant et je vérifie ce qu'on me dit :
# file /usr/share/man/man1/git.1.gz
/usr/share/man/man1/git.1.gz: broken symbolic link to
`/etc/alternatives/git.1.gz'
Il est possible
de man-db qui détecte une erreur :
/etc/cron.daily/man-db:
mandb: attention: /usr/share/man/man1/git.1.gz est un lien symbolique
flottant
Alors moi je suis pas contrariant et je vérifie ce qu'on me dit :
# file /usr/share/man/man1/git.1.gz
/usr/share/man/man1/git.1.gz: broken symbolic link
Bonjour,
Je viens avec un sujet qui me gène depuis quelques temps sur ma Debian
Etch : j'ai installé il y a quelques mois le paquet git via apt-get et
depuis à chaque nouveau paquet que j'installes, j'ai le lendemain un
mail de man-db qui détecte une erreur :
/etc/cron.daily/man-db:
mandb
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 different archs
| 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 unsubscribe. Trouble? Contact
(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 explanation
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-ro)
Hmm. nosuid
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 hypothetical user looks at a frequently used man page
I seem to remember
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
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 db,
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.1x: No
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
`.so'
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 symlink
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/xtrap.1x: No such file or directory
mandb: warning
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
This in spite of all the evidence
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 would be a lot easier to use the -L option and do it in one command
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-emulator.1.gz is a dangling
symlink
This in spite
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-terminal-emulator.1.gz
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-emulator.1.gz
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
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: warning: /usr/share/man/man3
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 man-db
$ cd
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 unstable. Do
: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 unstable. Do you know how
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
Frédéric Bothamy wrote:
* Jeremie Koenig [EMAIL PROTECTED] [2003-01-15 09:18] :
On Wed, Jan 15, 2003 at 08:21:33AM +0100, Raymond Gree wrote:
voila depuis quelques jour mon PC WOODY fonctionne 24/24
j'obtiens depuis le message:
/etc/cron.daily/man-db:
start-stop-daemon: user `man
Bonjour a tous,
voila depuis quelques jour mon PC WOODY fonctionne 24/24
j'obtiens depuis le message:
/etc/cron.daily/man-db:
start-stop-daemon: user `man' not found
run-parts: /etc/cron.daily/man-db exited with return code 2
je pense que c'est une operation periodique mais je n'arrive
On Wed, Jan 15, 2003 at 08:21:33AM +0100, Raymond Gree wrote:
voila depuis quelques jour mon PC WOODY fonctionne 24/24
j'obtiens depuis le message:
/etc/cron.daily/man-db:
start-stop-daemon: user `man' not found
run-parts: /etc/cron.daily/man-db exited with return code 2
je pense que
* Jeremie Koenig [EMAIL PROTECTED] [2003-01-15 09:18] :
On Wed, Jan 15, 2003 at 08:21:33AM +0100, Raymond Gree wrote:
voila depuis quelques jour mon PC WOODY fonctionne 24/24
j'obtiens depuis le message:
/etc/cron.daily/man-db:
start-stop-daemon: user `man' not found
run-parts
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
Satz- und Datentechnik Günter Knab
B|ro f|r Systemanalyse und angewandte Mathematik
Geiselhofer Strasse 5
92272 Lintach
tel:+49.9627.91261
fax:+49.9627.91262
mailto:[EMAIL PROTECTED]
http://www.asamnet/~knabguen
On Mon, 11 Feb 2002, D E Radel wrote:
Hi everyone.
Error installing man-db
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 you!
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 runs with root privileges:
$ ll /usr/lib/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 4096 Sep 26 00:55 ./
drwxr-xr-x 131 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 some time
now, and I
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 remember anyone complaining about this...
I'm not sure what caused the permissions to be that way originally
(can't have
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 4096 Sep 26 00:55
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 || run-parts --report
/etc/cron.weekly
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 'man',
because running
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 to remove
stale files from the /var/cache
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: SHELL=/bin/sh
X-Cron-Env:
PATH=/usr/local/sbin:/usr/local/bin:/sbin
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 return code 3
my
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 can try.
...
run-parts: /etc
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 exit status 1
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: error processing man-db (--configure):
subprocess post
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 that I
should have
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 the groff item still shows
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
Hola a la lista
He estado recompilando el dsc 66 de man-db, y me ha ocurrido una cosa curiosa
El configure que viene incluido, no soporta --with-db=db2, pero si lo borro,
se regenera y entonces si lo soporta, es como si el configure y el configure.in
no tuvieran que ver uno con otro.
¿Puede
On Sat, Aug 29, 1998 at 08:52:14AM +0200, Angel Vicente Perez wrote:
El configure que viene incluido, no soporta --with-db=db2, pero si
lo borro, se regenera y entonces si lo soporta, es como si el
configure y el configure.in no tuvieran que ver uno con otro.
¿Puede ser un bug?
Desde mi
Hola a la lista...
Estoy viendo el paquete man-db_2.3.10-65, en su version fuente, y he visto que
el instalable que genera es de la forma:
man-db_2.3.10-63*.deb
¿Esto es un error?
En el fichero rules, se establece la variable my-version=63.
Saludos.
Angel Vicente Perez
Dpto. Informática
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 man-db
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
experienced this ?
Yes. Please refer to the Debian-user faq:
http://www.debian.org/cgi-bin/fom?file=58showEditCmds=1
it´s because the database of man-db is corrupted.
The above reference (fom?...) is claims that the DB is getting corrupted and
that rebuliding it solves the problem
:
http://www.debian.org/cgi-bin/fom?file=58showEditCmds=1
it´s because the database of man-db is corrupted.
The above reference (fom?...) is claims that the DB is getting corrupted and
that rebuliding it solves the problem. This is seems to an answer.
However, it is also said that the DB
... 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
--
TO UNSUBSCRIBE FROM THIS MAILING
.
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.
dpkg: error processing man-db (--install):
subprocess post-installation script
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
You
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 hot potato between man-db,
boot-floppies and perl-base), came
to the Debian-user faq:
http://www.debian.org/cgi-bin/fom?file=58showEditCmds=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 48 1E 05 93 3A A7 10 73 37
--
TO UNSUBSCRIBE
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
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
output of dpkg -l '*man*' is here:
pn man none (no description available)
un man-aeb none (no description available)
un man-browser none (no description available)
ii man-db 2.3.10-38 Display the on-line manual.
ii manpages1.15-4
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
[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 random times. Perhaps
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've
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 have
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
system
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.
Configuration of man-db fails for lack
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] .
-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 for the swallows,
It sets the sand
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
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
Errors
80 matches
Mail list logo
