The mailing list for listmasters using Sympa

["antonelli@cnaf" <address@concealed>]

Hi Stephen,

thank you for your detailed description and log specifying (it could 
have been a RTFM answer but you avoided it :-) );

thank you
cheers
Stefano

On 7/19/21 16:06, Stephen Jarjoura wrote:
> sync_include is  a global task.
>
>
>           Global model paths
>
>     The task manager daemon checks if a version of a global task model
>     exists in different directories in the following order:
>
>       *
>
>         |$SYSCONFDIR|
>         
> <https://sympa-community.github.io/manual/layout.html#sysconfdir>|/tasks/|;
>
>       *
>
>         |$DEFAULTDIR|
>         
> <https://sympa-community.github.io/manual/layout.html#defaultdir>|/tasks/|.
>
> ...
>
>
>         The |sync_include| task
>
>     An exception in the realm of tasks in Sympa, the |sync_include| task
>     accepts one and only one model : |sync_include.ttl.task|. It’s
>     useless to try and create other versions of this task, they will be
>     ignored. There exists a configuration parameter related to
>     |sync_include|, though, but it doesn’t set the model used. */It is
>     the ttl
>     <https://sympa-community.github.io/gpldoc/man/sympa_config.5.html#ttl> 
> parameter./*
>     It will just set the length of time between two synchronizations.
>
> https://sympa-community.github.io/manual/customize/basics-tasks.html 
> <https://sympa-community.github.io/manual/customize/basics-tasks.html>
>
> The "ttl" parameter controls when a sync_include task runs, the default 
> is 1 hour (3600 seconds).
>
>
>           |ttl|
>
>     Inclusions timeout
>
>       *
>
>         Format:
>
>         Number of seconds.
>
>       *
>
>         Default:
>
>         |3600| (seconds)
>
>       *
>
>         Context:
>
>         list (|config|), site (|sympa.conf|)
>
>     Sympa caches user data extracted using the include parameter. Their
>     TTL (time-to-live) within Sympa can be controlled using this
>     parameter. The default value is 3600
>
> https://sympa-community.github.io/gpldoc/man/sympa_config.5.html 
> <https://sympa-community.github.io/gpldoc/man/sympa_config.5.html>
>
> The log entries look like this:
>
>     Jul 19 09:54:36 sympahost task_manager[122261]: notice
>     Sympa::Spindle::ProcessTask::_execute() Running task Sympa::Task
>     
> <date=1626702875;label=INIT;model=sync_include;address@concealed>
>     Jul 19 09:54:36 sympahost task_manager[122261]: notice
>     Sympa::Spindle::ProcessTask::do_next() line 5 of sync_include:
>     next(1626706476, INIT)
>     Jul 19 09:54:36 sympahost task_manager[122261]: notice
>     Sympa::Spool::store() Sympa::Task
>     
> <date=1626706476;label=INIT;model=sync_include;address@concealed>
>     is stored into Sympa::Spool::Task as
>     <address@concealed>
>
>
>
> --
> Stephen A. Jarjoura
> Collaborative Services
>
>
> On Mon, Jul 19, 2021 at 5:48 AM antonelli@cnaf 
> <address@concealed <mailto:address@concealed>> 
> wrote:
>
>     Dear All,
>
>     sorry
>
>     [Sympa 6.2.62 multi-domain on CentOS 7.9]
>
>     the rest is the same
>
>     cheers Stefano
>
>     On 7/19/21 11:45, antonelli@cnaf wrote:
>      > Dear All,
>      >
>      > [Sympa 6.2.58 multi-domain on CentOS 7.9]
>      >
>      > one users is including/excluding members of a list from external
>      > source
>      > (in particular it's a text file served from
>      > https://some_server/a_file.txt <https://some_server/a_file.txt>)
>     and it works.
>      >
>      > I'm not able to understand if and how many times a day the
>     process runs
>      > and
>      > which is the process which updates the subscribers list apart from a
>      > manual syncronization.
>      >
>      > I've tried to check sympa.log grepping "include" and I find only
>     lists
>      > including from LDAP source and, even in this case, I do not find a
>      > regular timestamp for a cron job running.
>      >
>      > Could you explain me how it works?
>      >
>      > thank you
>      > cheers
>      > Stefano
>      >