Univention-pkgdb-scan --clean

german

#1

seit einiger Zeit erhalte ich folgende Fehlermeldung:


[color=#000080]/etc/cron.weekly/univention-pkgdb-clean:
Usage: univention-pkgdb-scan [options]
Scan all packages in the local system and send this data to the database pkgdb.

univention-pkgdb-scan: error: no such option: --clean
run-parts: /etc/cron.weekly/univention-pkgdb-clean exited with return code 2[/color]

das zugehörige Script dazu nachstehend:


[color=#000080]#!/bin/sh

Univention Package Database

script to clean pkgdb from old entries

Copyright 2004-2011 Univention GmbH

univention.de/

All rights reserved.

The source code of this program is made available

under the terms of the GNU Affero General Public License version 3

(GNU AGPL V3) as published by the Free Software Foundation.

Binary versions of this program provided by Univention to you as

well as other copyrighted, protected or trademarked materials like

Logos, graphics, fonts, specific documentations and configurations,

cryptographic keys etc. are subject to a license agreement between

you and Univention and not subject to the GNU AGPL V3.

In the case you use this program under the terms of the GNU AGPL V3,

the program is provided in the hope that it will be useful,

but WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public

License with the Debian GNU/Linux or Univention distribution in file

/usr/share/common-licenses/AGPL-3; if not, see

http://www.gnu.org/licenses/.

PATH=/usr/sbin:/usr/bin:/sbin:/bin

/usr/sbin/univention-pkgdb-scan --clean[/color]

Da die Option “–clean” nicht existiert würde ich gern wissen, was am sinnvollsten ist,
um die Fehlermeldung künftig zu unterbinden.

Freundliche Grüße
htsth


#2

Hallo,

der Cron-Job /etc/cron.weekly/univention-pkgdb-clean ist obsolet und kann gelöscht werden (das hätte eigentlich während eines Updates automatisch passieren sollen, in ihren Fall hat das wohl aber nicht funktioniert).

Bitte löschen Sie die Datei /etc/cron.weekly/univention-pkgdb-clean und, falls vorhanden, auch /etc/univention/templates/files/etc/cron.weekly/univention-pkgdb-clean.

Danach müsste die Cron-Config wohl mit “/etc/init.d/cron reload” einmal neu eingelesen werden.

Mit freundlichen Grüßen
Felix Botner