forum.opsi.org

Hi there!
We are evaluating your product, and i have three quick questions for you, all related to handling Debian servers updates:
How does opsi handles
1) (prompt for) Configuration changes? (Packages upgrades that ask to keep, replace configuration files)
2) "Kept back packages"?
3) packages upgrades that need a reboot to take place (eg kernel upgrades)?

Thanks!

Hi,

Cosimo hat geschrieben:We are evaluating your product, and i have three quick questions for you, all related to handling Debian servers updates:

as Debian can be the OS for the server or an client I'd have to ask in which role is Debian in this question?


Kind regards

Niko

Sorry.
I meant: "What happens, client side, by using opsi to update Debian Systems, in those scenarios".

OPSI_SERVER sends DEBIAN_SYSTEM1 the command "Update yourself". DEBIAN_SYSTEM1 starts upgrade process, and finds itself in one (or all) of the situations shown below.
Am i notified?
How does DEBIAN_SYSTEM1 is instructed to react?
How does OPSI_SERVER "works" in those scenarios?

Thanks!
Cosimo

Cosimo hat geschrieben: Am i notified?

You will get a feedback in the configed

Cosimo hat geschrieben: How does DEBIAN_SYSTEM1 is instructed to react?

It simpyl calls the shell commands given by the opsiscript script

Cosimo hat geschrieben: How does OPSI_SERVER "works" in those scenarios?

it serves as the host of opsiscript scripts and gets the feedback of such tasks

This is the expected way when you use the l-system-update package to do this

You can also edit the package to work it in another way if you need it

Cheers
mathias