threerings / splatd Goto Github PK

In addition to the record itself changing, a group modification may also
trigger a per-record configuration change. Splat currently does not recognize
group changes, and thus does not apply configuration changes.

An example of this is home directory creation. If a user is not in a group
required for home directory creation, the directory will not be created until
splat is restarted, or the user's LDAP record is modified, even after the user
is added to the requisite group.

The fix for this seems to be checking both the record's modification time, as
well as the modification time of any groups of which the record is a member.

Similarly to how it is possible to run a script for the homedir creation 
helper, it would be nice to be 
able to run a script to do extra cleanup when an account is purged. This would 
aid in, for example, 
removing Apache configs generated by a homedir creator that makes Apache 
configuration files for 
each user on a WebDAV file server.

Sometimes users have files that are their responsibility in their home 
directory that they may not 
have permission to delete, e.g. files that need to be writeable by the user 
running the web server. It 
may be desirable to delete these files anyway when a home directory is purged. 

I'm not certain if implementing this feature really is all that great of an 
idea though, because 
deleting everything as root has a lot of potential to cause damage. An 
alternative solution may be 
to specify a list of other users to try dropping privileges to if the first 
deletion as the user itself 
fails.

If "Level debug" is set in a <logfile> subsection in splat.conf, messages will 
only be logged at level 
info (the default) or whatever is set in the global Level for the entire 
<Logging> section. I think the 
level can be properly set in <syslog> subsections though. Based on my 
uncertainty I've just 
updated the documentation to mention only a global Level setting for the entire 
<Logging> section.

This could be related to the version of ZConfig used. On tests that showed this 
I was using ZConfig 
2.3.1.