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

doc - must use ns_job_done on persistent jobs #1451

Closed
389-ds-bot opened this issue Sep 12, 2020 · 2 comments
Closed

doc - must use ns_job_done on persistent jobs #1451

389-ds-bot opened this issue Sep 12, 2020 · 2 comments
Labels
closed: duplicate Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48120

  • Created at 2015-03-10 06:08:48 by rmeggins (@richm)
  • Closed as Duplicate
  • Assigned to nobody

You must use ns_job_done on persistent jobs.
Persistent I/O job callbacks will not be called when the client closes the connection. You cannot depend on being able to call ns_job_done on the persistent job when the connection is closed and the read callback is called. For non-persistent I/O jobs, the read callback will be called when the connection is closed by the client. We need to make sure this behavior is documented - or perhaps it is only a libevent thing?

@389-ds-bot 389-ds-bot added the closed: duplicate Migration flag - Issue label Sep 12, 2020
@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2017-02-11 23:01:46

Metadata Update from @richm:

  • Issue set to the milestone: N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant