Univention Bugzilla – Bug 40347
UCS@school: make creation of NETLOGON scripts in /var/lib/samba/netlogon the default
Last modified: 2016-10-04 13:24:48 CEST
Right now, NETLOGON scripts are created underneath /var/lib/samba/sysvol/DOMAIN/scripts/user and are synchronised via sysvol-sync. For a 15.000 user environment this means 15.000 more files to check for sysvol-sync (total size of ~120MB). Therefore, the following should be the default: http://docs.software-univention.de/ucsschool-handbuch-4.1.html#school:windows:samba4netlogon
The change is done on fresh UCS@school DCs only. If both UCRVs are unchanged (empty), they are set: samba/share/netlogon/path=/var/lib/samba/netlogon ucsschool/userlogon/netlogon/path=/var/lib/samba/netlogon/user r71379 : ucs-school-metapackage 9.0.1-5.177.201608031259
From what I know about postinst scripts the way it is called is wrong: if [ "$1" = "configure" ] ; then .... else; ... the ucr set code ... fi So this wouldn't be called only on new installations but also on "abort-remove", etc.
Do we need to set this on administrative servers as well? Why don't we set these values in the joinscript?
r72709: ensure UCRVs are set on new installations only > Do we need to set this on administrative servers as well? This was agreed upon with Sönke. * There are installations with many teachers. * It is easier to maintain if there are the same settings "everywhere". > Why don't we set these values in the joinscript? * No need to manually run the join script on slaves, when updating. * There is no reliable way to ensure a first-time run with join scripts (count is reset when rejoining).
FYI: The package wasn't build. I did that. OK: ucr variables are set in new installation OK: updating UCS@school doesn't set the variables The variables aren't set with "?" so it's not possible to define them prior to installing UCS@school. OK: YAML REOPENED: the variables aren't unset on purge. @Sönke: what is the policy here? UCR should imho really make it possible to define defaults. that would fix all the unset problems.
(In reply to Florian Best from comment #5) > FYI: The package wasn't build. I did that. > > OK: ucr variables are set in new installation > OK: updating UCS@school doesn't set the variables > > The variables aren't set with "?" so it's not possible to define them prior > to installing UCS@school. > > OK: YAML > > REOPENED: the variables aren't unset on purge. > @Sönke: what is the policy here? Hmmm... I split that off into bug 42469. → back to RESOLVED > UCR should imho really make it possible to define defaults. that would fix > all the unset problems. Would be better, but would not solve all problems.
OK
(In reply to Florian Best from comment #3) > Do we need to set this on administrative servers as well? I would say "yes". Due to the same reasons Daniel already wrote. Additionally the sysvol share is also synced on administrative DC slaves against the master. So we might have the same problems there (but in a smaller scale). > Why don't we set these values in the joinscript? Too late. The listener module for logon scripts is restarted/reinitialized before the ucs-school join scripts are run through. What other kind of benefit should it have by setting the values in the join script?
UCS@school 4.1 R2 v5 has been released. http://docs.software-univention.de/changelog-ucsschool-4.1R2v5-de.html If this error occurs again, please clone this bug.