apt-get udate Probleme mit neuer Webmin version

Du kommst mit der Installation nicht voran oder willst noch was nachfragen? Schau auch in den "Tipps und Tricks"-Bereich.
Antworten
Benutzeravatar
Neroz999
Beiträge: 215
Registriert: 12.01.2003 22:20:24
Wohnort: Bay. Monte Carlo = München

apt-get udate Probleme mit neuer Webmin version

Beitrag von Neroz999 » 28.06.2003 20:19:05

tux:~# apt-get update
Hit http://security.debian.org stable/updates/main Packages
Hit http://security.debian.org stable/updates/main Release
Hit http://non-us.debian.org proposed-updates/non-US/main Packages
Hit http://non-us.debian.org proposed-updates/non-US/main Release
Hit http://non-us.debian.org proposed-updates/non-US/contrib Packages
Hit http://non-us.debian.org proposed-updates/non-US/contrib Release
Hit http://non-us.debian.org stable/non-US/main Packages
Hit http://non-us.debian.org stable/non-US/main Release
Hit http://non-us.debian.org stable/non-US/main Sources
Hit http://non-us.debian.org stable/non-US/main Release
Hit http://non-us.debian.org stable/non-US/main Packages
Hit http://non-us.debian.org stable/non-US/main Release
Hit http://non-us.debian.org stable/non-US/main Sources
Hit http://non-us.debian.org stable/non-US/main Release
Hit ftp://ftp.de.debian.org woody/main Packages
Hit ftp://ftp.de.debian.org woody/main Release
Hit ftp://ftp.de.debian.org proposed-updates/main Packages
Hit ftp://ftp.de.debian.org proposed-updates/main Release
Hit ftp://ftp.de.debian.org proposed-updates/contrib Packages
Hit ftp://ftp.de.debian.org proposed-updates/contrib Release
Hit ftp://ftp.de.debian.org stable/main Packages
Hit ftp://ftp.de.debian.org stable/main Release
Hit ftp://ftp.de.debian.org stable/main Sources
Hit ftp://ftp.de.debian.org stable/main Release
Hit ftp://ftp.de.debian.org stable/main Packages
Hit ftp://ftp.de.debian.org stable/main Release
Hit ftp://ftp.de.debian.org stable/main Sources
Hit ftp://ftp.de.debian.org stable/main Release
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct
You're upgrading mon from version . Version 0.99.1 of mon made some
changes to its default behavior:

- The old "comp_alerts" behavior for a period section is now
the default. This means you won't get an upalert unless the
corresponding alert was triggered. To get the old behavior,
specify "no_comp_alerts" in the period section.

- The old "summary" option for alertevery is now the default.
This means that a monitor failure which leaves the summary
line (first line of output) the same but changes the body
doesn't trigger a new alert. To get the old behavior, append
"no_summary" to the alertevery line.

The corresponding old options in mon.cf ("comp_alerts" and "alertevery
... summary") are accepted, but they don't do anything.

If you need to change your mon.cf, you can you can either make your
changes while I wait (from another window or the like), or I can abort
the configuration of the new mon package so the daemon won't be started.
NB: The mon daemon will still be started after the next system reboot,
even if dpkg doesn't finish configuration of the mon package.

The new behavior is generally more useful, and most people will want
simply to leave their mon.cf as-is and continue with configuration so as
to use the new defaults.

kann mir mal einer sagen was der da will, da mein english net so gut ist und ich auch kein Debian gott bin :roll: leider :P

Benutzeravatar
Rebell
Beiträge: 997
Registriert: 14.01.2003 20:36:53
Wohnort: Dresden

Beitrag von Rebell » 28.06.2003 21:23:35

Hast du schonmal versucht was er dir sagt?

dpkg --configure -a
come to daddy, windowlicker!
get m:ke - http://get-mike.de

Benutzeravatar
Neroz999
Beiträge: 215
Registriert: 12.01.2003 22:20:24
Wohnort: Bay. Monte Carlo = München

Beitrag von Neroz999 » 28.06.2003 23:28:10

das habe ich noch rauslesen können

aber was ich dann einstelllen muss is mir ein rätsel

Antworten