First Last Prev Next    This bug is not in your last search results.
Bug 19749 - univention-maintenance rebootet bereits vor actualise und security-updates
univention-maintenance rebootet bereits vor actualise und security-updates
Status: RESOLVED DUPLICATE of bug 37231
Product: UCS
Classification: Unclassified
Component: Update - univention-updater
UCS 2.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-08-30 08:39 CEST by Philipp Hahn
Modified: 2018-04-14 13:51 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2010-08-30 08:39:41 CEST 
Aktiviert man in den "Paketpflege Einstellungen" die Option "Nach Paketpflege neu starten", wird folgender Cron-Eintrag (am Beispiel Montag 8:00 Uhr) in "/etc/cron.d/univention-maintenance" generiert:

 # cron job for update
 0 8 * * 1  root /usr/sbin/univention-updater local  --reboot=now --silent; /usr/sbin/univention-actualise --dist-upgrade --silent; /usr/sbin/univention-security-update local --silent

Ein Neustart wird bereits durch "univention-updater" ausgeführt, so daß "univention-actualise" und "univention-security-update" keine Chance mehr haben ihre Updates einzuspielen.

Der Reboot sollte erst nach Einspielen aller Updates stattfinden.
Comment 1 Philipp Hahn univentionstaff 2014-12-10 15:59:25 CET 

*** This bug has been marked as a duplicate of bug 37231 ***
First Last Prev Next    This bug is not in your last search results.