#2231 RFE: Drop the monitor process
Closed: wontfix 5 months ago by pbrezina. Opened 6 years ago by jhrozek.

In the future we migth consider dropping the monitor process by default and rely on systemd to monitor the subprocesses instead.

Some parts of the monitor would have to be moved elsewhere, such as inotify watch on the /etc/resolv.conf, reading the config or the libnl integration. One possibility might be to let the monitor still do the global tasks such as inotify and only deprecate the pings.


Moving to 1.15 as per the triage on Feb 13

milestone: NEEDS_TRIAGE => SSSD 1.15 beta

Fields changed

rhbz: => 0

Fields changed

mark: => 0
milestone: SSSD 1.15 beta => SSSD 1.14 beta

We're taking baby steps towards this goal. As a first phase, we need to merge the socket activation patches Simo posted.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog
sensitive: => 0

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

3 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

5 months ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 months ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3273

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata