The mailing list for listmasters using Sympa

[Christian Dahlhausen <address@concealed>]

Just a gut feeling, but maybe it helps just to add an owner entry in the list config file. Maybe the parameter is mandatory but as long as it has an owner from where ever (owner_include in this case) it could be fine. 

I found that having more load on logging (just increasing the log level) decreases the Sympa (wwsympa) performance significantly.

Christian

On Wed, Feb 24, 2010 at 4:43 PM, Kartik Subbarao <address@concealed> wrote:

I'm seeing these kinds of messages very frequently in syslog:

Feb 24 13:24:52 sympa-dev task_manager[11880]: List::_load_admin_file() Missing parameter "owner" in /home/sympa/list_data/test2/config
Feb 24 13:24:52 sympa-dev task_manager[11880]: List::_include_users_ldap_2level() 2 new users included from LDAP query
Feb 24 13:31:52 sympa-dev task_manager[11880]: List::_load_admin_file() Missing parameter "owner" in /home/sympa/list_data/test2/config
Feb 24 13:31:52 sympa-dev task_manager[11880]: List::_include_users_ldap_2level() 2 new users included from LDAP query
[...]

For this list, there is no 'owner' parameter specified. Instead, I'm using 'owner_include' to pull in the list owners dynamically from LDAP.

I'm concerned about the unnecessary errors piling up in the log file, as well as the fact that it seems to see the owners as being "new" each time. Since we will be adding lots of LDAP-sourced groups on this server, I'm concerned that this will create extra levels of overhead.

Any suggestions for working around or resolving this situation?

Thanks,

       -Kartik

-- 
-----------------------------------------------------------
Christian Dahlhausen, Network Systems Engineer
University of Virginia - ITC Network Systems 
PO Box 400324, 2015 Ivy Road, Charlottesville, VA 22904