summaryrefslogtreecommitdiff
path: root/src/monitor
AgeCommit message (Collapse)AuthorFilesLines
2013-06-26Revert "Implicitly activate the PAC responder for AD provider"Sumit Bose1-2/+1
This reverts commit 7527ec8ab2b79ec576ace2da9e2c158b849adfa6.
2013-06-06Implicitly activate the PAC responder for AD providerSumit Bose1-1/+2
2013-05-21Check NSCD configuration fileOndrej Kos1-6/+26
https://fedorahosted.org/sssd/ticket/1785 nscd.conf file is now checked for the presence of caching settings for databases controlled by SSSD. Syslog warning is now written only if NSCD is running with interfering configuration or if configuration file couldn't be loaded. New configure option added to support non-standard locations --with-nscd-conf=PATH (defaultly set to /etc/nscd.conf) This is just a workaround until the following bugzilla is resolved: https://bugzilla.redhat.com/show_bug.cgi?id=963908
2013-04-26DB: Switch to new libini_config APIOndrej Kos1-2/+0
https://fedorahosted.org/sssd/ticket/1786 Since we need to support the old interface as well, the configure scritp is modified and correct ini interface is chosen.
2013-04-12Confusing error messages for invalid sssd.confAriel Barria1-9/+11
https://fedorahosted.org/sssd/ticket/1625 Amending errors messages and add other error codes to be more specific and avoid confusion.
2013-04-02Improve syslog message when configuration cannot be loadedAriel Barria1-1/+3
https://fedorahosted.org/sssd/ticket/1414 Error code was added and strerror(errno) to show cause in sss_log
2013-03-27Provide libnl3 supportOndrej Kos1-50/+100
https://fedorahosted.org/sssd/ticket/812 Update the monitor code to be using the new libnl3 API. Changed configure option --with-libnl By default, it tries to build with libnl3, if not found, then with libnl1, if this isn't found either, build proceeds without libnl, just with warning. Specifing --with-libnl=<libnl3|libnl1|no> checks for the specific given version, if not found, configure ends with error.
2013-03-05Remove the alt_db_path parameter of sysdb_initMichal Zidek1-1/+1
This parameter was never used. https://fedorahosted.org/sssd/ticket/1765
2013-02-10Add function get_next_domain()Simo Sorce1-5/+5
Use this function instead of explicitly calling domain->next This function allows to get the next primary domain or to descend into the subdomains and replaces also get_next_dom_or_subdom()
2013-01-15Refactor sysdb initializationSimo Sorce1-2/+1
Change the way sysdbs are initialized. Make callers responsible for providing the list of domains. Remove the returned array of sysdb contexts, it was used only by sss_cache and not really necessary there either as that tool can easily iterate the domains. Make sysdb ctx children of their respective domains. Neither sysdb context nor domains are ever freed until a program is done so there shouldn't be any memory hierarchy issue. As plus we simplify the code by removing a destructor and a setter function.
2012-12-18AUTOFS: Clear enum cache if a request comes in from the sss_cacheJakub Hrozek2-0/+9
In order for sss_cache to work correctly, we must also signal the autofs responder to invalidate the hash table requests.
2012-12-18RESPONDERS: Create a common file with service names and versionsJakub Hrozek1-1/+1
The monitor sends calls different sbus methods to different responders. Instead of including headers of the particular responders directly in monitor, which breaks layering a little, create a common header file that will be included from src/responder/common/
2012-12-04do not crash when id_provider is not setPavel Březina1-0/+6
https://fedorahosted.org/sssd/ticket/1686
2012-11-28Monitor quit when not exists no process no stopsAriel O. Barria1-1/+3
https://fedorahosted.org/sssd/ticket/1669
2012-11-26debug: print fatal and critical errors if debug level is unresolvedMichal Zidek1-6/+0
If global variable debug_level has value SSSDBG_UNRESOLVED, we should print at least fatal and critical errors. https://fedorahosted.org/sssd/ticket/1345
2012-11-19Restart services with a delay in case they are restarted too oftenJakub Hrozek1-14/+59
In case a service is restarted while the DP is not ready yet, it gets restarted again immediatelly, which means the DP might still not be ready. The allowed number of restarts is then depleted quickly. This patch changes the restart mechanism such that the first restart happens immediatelly, the second is scheduled after 2 second, then 4 etc.. https://fedorahosted.org/sssd/ticket/1528
2012-11-19Display more information on DB version mismatchOndrej Kos1-0/+1
https://fedorahosted.org/sssd/ticket/1589 Added check for determining, whether database version is higher or lower than expected. To distinguish it from other errors it uses following retun values (further used for appropriate error message): EMEDIUMTYPE for lower version than expected EUCLEAN for higher version than expected When SSSD or one of it's tools fails on DB version mismatch, new error message is showed suggesting how to proceed.
2012-11-14Always start PAC responder if IPA ID provider is configuredSumit Bose1-0/+72
Since the PAC responder is used during the authentication of users from trusted realms it is started automatically if the IPA ID provider is configured for a domain to simplify the configuration. Fixes https://fedorahosted.org/sssd/ticket/1613
2012-11-08Monitor: Better debugging for ping timeoutsStephen Gallagher1-0/+8
2012-11-06create pid file immediately after fork againPavel Březina1-25/+4
Related to https://fedorahosted.org/sssd/ticket/1357 We realized that sysv and systemd does not use pid file existence as a notification of finished initialization. Therefore, we create the pid file in server_setup() again. We are removing check_file() from monitor main(), it is handled by server_setup() during pid file creation. This check was previously included in e7dd2a5102ba6cfd28be6eccdd62768e9758d9f4.
2012-11-06exit original process after sssd is initializedPavel Březina1-0/+26
https://fedorahosted.org/sssd/ticket/1357 Neither systemd or our init script use pid file as a notification that sssd is finished initializing. They will continue starting up next service right after the original (not daemonized) sssd process is terminated. If any of the responders fail to start, we will never terminate the original process via signal and "service sssd start" will hang. Thus we take this as an error and terminate the daemon with a non-zero value. This will also terminate the original process and init script or systemd will print failure.
2012-11-06make monitor_quit() usable outside signal handlerPavel Březina1-14/+26
2012-11-01Monitor: read the correct SIGKILL timeout for providers, tooJakub Hrozek1-33/+41
https://fedorahosted.org/sssd/ticket/1602
2012-10-29Include talloc log in our debug facilityMichal Zidek1-1/+1
https://fedorahosted.org/sssd/ticket/1495
2012-10-05do not create pid file twicePavel Březina1-1/+6
If a provider is terminated and the monitor tries to restart it, it goes again through mark_service_as_started() which will try to create pid file again because number of running services didn't change. Because the pid file cannot be created twice, it will not return EOK and the whole SSSD is terminated.
2012-10-04Check for existing pidfile before starting the providersJakub Hrozek1-17/+15
After we switched to writing pidfile after the responders started, we forgot that starting a second SSSD instance would first overwrite the pipes and sockets and only then the SSSD would find out there already is a pidfile. This patch checks for existing pidfile before proceeding with startup.
2012-10-04Change the log level of two DEBUG messages in check_domain_rangesJakub Hrozek1-4/+5
https://fedorahosted.org/sssd/ticket/1562
2012-10-02monitor: create pid file after all responders are startedPavel Březina1-4/+36
https://fedorahosted.org/sssd/ticket/1357
2012-10-02Fix few coding style issuesPavel Březina1-3/+6
2012-09-24sss_cache tool invalidates records in memory cache.Michal Zidek2-1/+12
2012-09-20Missing resolv.conf should be non-fatalAriel Barria1-17/+43
https://fedorahosted.org/sssd/ticket/1371
2012-09-12Remove obsolete commentSimo Sorce1-5/+0
Made obsolete by commit e2d17ea806d273784b621583dd0490c2f69f237d
2012-09-05SIGUSR2 should force SSSD to reread resolv.conf as wellAriel Barria1-2/+19
2012-08-07monitor: set debug level when unable to load configurationPavel Březina1-0/+6
https://fedorahosted.org/sssd/ticket/1345 When the monitor is unable to load configuration and non debug level is set (e.g. when sssd is started via 'service'), none message was saved into logs. This patch forces debug messages to be written in this scenario.
2012-08-07Add end of line to debug messagePavel Březina1-2/+2
2012-06-21PAC responder: add basic infrastructureSumit Bose1-1/+1
This adds only the basic outline of the PAC responder, it won't support any operations, it will just start and initialize itself.
2012-06-20Move some debug lines to new debug log levelsStef Walter1-2/+2
* These are common lines of debug output when starting up sssd https://bugzilla.redhat.com/show_bug.cgi?id=811113
2012-04-20Convert read and write operations to sss_atomic_readJakub Hrozek2-32/+29
https://fedorahosted.org/sssd/ticket/1209
2012-04-20Make the monitor SIGKILL time configurableJakub Hrozek1-3/+23
https://fedorahosted.org/sssd/ticket/1119
2012-04-09netlink integration: ensure that interface name is NULL-terminatedJakub Hrozek1-1/+2
In the unlikely case that the interface name was IFNAMSIZ bytes long or longer, strncpy wouldn't NULL-terminate the buffer. Copy one byte less to ensure the buffer is NULL-terminated.
2012-02-23libnl: fix the path to phy80211 subdirectoryJakub Hrozek1-4/+20
2012-02-21Don't give memory context in confdb where not neededJan Zeleny2-5/+5
2012-02-21remove unused functionJakub Hrozek1-20/+0
2012-02-07SSH: ResponderJan Cholasta1-1/+2
2012-02-05AUTOFS: responderJakub Hrozek1-1/+1
2011-12-20MONITOR: use sigchld handler for monitoring SSSD servicesStephen Gallagher1-177/+159
2011-12-16SUDO Integration - responderPavel Březina1-1/+1
2011-12-13Cancel ping_check if service goes awayJakub Hrozek1-1/+14
https://fedorahosted.org/sssd/ticket/1090
2011-12-08Added sssd --version optionPavel Březina1-2/+10
https://fedorahosted.org/sssd/ticket/953
2011-11-22Set more strict permissions on keyringSimo Sorce1-0/+27
We want to confine access to the keyring to the current process and not let root easily peek into the keyring contents.
generated by cgit (git 2.34.1) at 2024-11-12 17:13:56 +0000