The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi,

First: a question: is the space occupied by these files a problem on your server? How many lists do you run?
Then, yes you can delete any old config file you want to. We never do this on our production server as keeping old versions of these files can help us understanding a problem and how it appeared.
However, there is no task in Sympa that purges the old config files. You can still define a cron task that deletes the files you don't need.

Regards,

Brightblade a écrit : Hello,

I'll try introduce my issue: When I modified a list's config a new config file is created and a backup for the last config is created too. I wanna know if you can set a max count for this kind of files. An example:

config     config.13  config.19  config.24  config.3   config.6     include_admin_user.lock  subscribers.closed.dump
config.0   config.14  config.2   config.25  config.30  config.7     include.lock             subscribers.closed.dump.back
config.1   config.15  config.20  config.26  config.31  config.8     message.footer.back
config.10  config.16  config.21  config.27  config.32  config.9     msg_count
config.11  config.17  config.22  config.28  config.4   config.lock  stats
config.12  config.18  config.23  config.29  config.5      stats.lock

Can I preserver only five of this files? Can I configure sympa for  purge the old config files?

Thanks in advance,

Regards

-- 
David Verdin
Comité réseau des universités