This repository has been archived on 2020-03-24. You can view files and clone it, but cannot push or open issues or pull requests.
quay/conf/init/service
Jimmy Zelinskie 2b84888c2f syslog: have syslog generate timestamps (#1585)
This is the more elegant solution to #1579.
2016-06-27 14:42:44 -04:00
..
buildlogsarchiver syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
buildmanager syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
gcworker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
gunicorn_registry syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
gunicorn_secscan syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
gunicorn_verbs syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
gunicorn_web syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
jwtproxy syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
logrotateworker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
nginx syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
notificationworker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
queuecleanupworker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
repositoryactioncounter syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
security_notification_worker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
securityworker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
service_key_worker syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
storagereplication syslog: have syslog generate timestamps (#1585) 2016-06-27 14:42:44 -04:00
syslog-ng runit: wait for syslog-ng before starting loggers (#1537) 2016-06-10 20:29:45 -04:00