Re: Linux und WAN Addon
Verfasst: 26 Aug 2021, 09:57
Das swaudit funktioniert wohl nicht im WAN-Modus ...
Code: Alles auswählen
# grep event_ -A4 /etc/opsi-client-agent/opsiclientd.conf
[event_default]
; === Event configuration
# Type of the event (string)
type = template
# Time in seconds after which a timer / custom event is triggered for the first time after event activation (int, 0 = disabled).
--
event_notifier_command = %opsiclientd_notifier.command% -s notifier/event.ini
# The desktop on which the event notifier will be shown on (all/current/default/winlogon)
event_notifier_desktop = all
# Block login while event is been executed (bool)
block_login = false
# Lock workstation on event occurrence (bool)
lock_workstation = false
--
post_event_command =
; === Sync/cache settings
# Sync configuration from local config cache to server (bool)
sync_config_to_server = false
--
[event_opsiclientd_start]
super = default
type = daemon startup
active = true
activation_delay = 10
--
[event_opsiclientd_start{cache_ready}]
use_cached_config = true
use_cached_products = true
[event_gui_startup]
super = default
type = gui startup
active = false
block_login = true
--
[event_gui_startup{user_logged_in}]
active = false
shutdown_warning_time = 3600
block_login = false
[event_gui_startup{cache_ready}]
active = false
use_cached_config = true
use_cached_products = true
action_user_cancelable = 3
--
[event_gui_startup{installation_pending}]
active = false
[event_on_demand]
super = default
type = custom
[event_on_demand{user_logged_in}]
shutdown_warning_time = 3600
[event_software_on_demand]
super = default
type = sw on demand
shutdown_warning_time = 3600
[event_sync]
super = default
type = template
process_actions = false
event_notifier_command =
sync_config_to_server = true
sync_config_from_server = true
cache_products = true
cache_dynamic_bandwidth = true
--
[event_timer]
super = sync
type = timer
active = true
interval = 3600
--
[event_net_connection]
super = sync
type = custom
active = true
[event_sync_completed]
super = default
type = sync completed
event_notifier_command =
process_actions = false
get_config_from_service = false
write_log_to_service = false
[event_sync_completed{cache_ready_user_logged_in}]
reboot = true
shutdown_user_cancelable = 10
shutdown_warning_time = 28000
[event_sync_completed{cache_ready}]
reboot = true
[event_on_shutdown]
super = default
type = custom
active = false
max_repetitions = 0
--
[event_on_shutdown{installation_pending}]
active = false
[event_silent_install]
super = default
type = custom
event_notifier_command =
process_shutdown_requests = false
action_processor_command = %action_processor.command% -productlist %action_processor_productIds% -silent
action_processor_desktop = winlogon
action_processor_timeout = 300
--
[event_timer_silentinstall]
super = silent_install
type = timer
active = false
interval = 21600
--
[event_user_login]
action_processor_command = %action_processor.command% /sessionid service_session /loginscripts /silent
active = false
Das klingt für mich nach dem korrekten Verhalten außer, dass ich mir nicht sicher bin, was mit traditionellem GUI-Startup-Event gemeint ist.also mir macht der WAN-Client leider ganz normalen GUI-Startup, d.h. er kontaktiert den Configserver und führt anstehende Aktionen durch. Wenn er vorher etwas gecached hat, werden die Aktionen aber im WAN-Modus abgearbeitet und erst beim nächsten mal kommt wieder ein traditionelles GUI-Startup-Event.