Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to set different running frequencies on different nodes? #310

Open
sht33 opened this issue Nov 15, 2024 · 3 comments
Open

How to set different running frequencies on different nodes? #310

sht33 opened this issue Nov 15, 2024 · 3 comments
Labels

Comments

@sht33
Copy link

sht33 commented Nov 15, 2024

I have two nodes, both with lsc installed,how to set different running frequencies on different nodes?Is it set in the lsc.xml configuration file? Or is it set using crontab -e?

@soisik
Copy link
Contributor

soisik commented Nov 19, 2024

Hello @sht33,

The frequencies of you task is indeed usually set using crontab -e -u lsc, so you just have to pick a different time for the second node.

@sht33
Copy link
Author

sht33 commented Nov 19, 2024

Hello @sht33,

The frequencies of you task is indeed usually set using crontab -e -u lsc, so you just have to pick a different time for the second node.

Is the default data synchronization method of lsc event-driven? For example, when the data in ldap changes, it will automatically trigger lsc to synchronize to the ad domain

@soisik
Copy link
Contributor

soisik commented Nov 19, 2024

Is the default data synchronization method of lsc event-driven?

There is no such thing as default behaviour. When launching a lsc task(s) you can eitheir use the -s(ync) or -a(sync) option to use the sync mode or the async (incremental) mode.

  • -s will do a full run and exit, usually it is set as a cron ;
  • -a will do a full run and will then search for updates periodically forever, usually it is set as service but I've also seen it set in a daily cron with a 24h timeout .

You can either use event-driven see https://www.lsc-project.org/documentation/latest/service_source_asyncldap.html, or if you prefer or your source ldap does not support it, use instead a regular ldap service and start it in async mode, and filterAsync, dateformat and interval to tune it, see last part in https://www.lsc-project.org/documentation/latest/service_source_ldap.html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants