Bug 714486
| Summary: | systemd fires services too fast | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Harald Reindl <h.reindl> |
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | elad, harald, johannbg, lpoetter, metherid, mschmidt, notting, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-20 11:46:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Harald Reindl
2011-06-19 15:31:12 UTC
I'm not a systemd developer and never written a service file, but I think you might want to use socket activation here. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers we are speaking here not only about unix-sockets it is also useles fire up a imap-proxy before the tcp-service on 127.0.0.1 is ready, there are a lot of other examples where it is strongly recommended that the start-order is clean the fault of syetmd for me is try to boot as fast as it can and all resulting troubles are seen as collateral damages - nobody is intesrest if his server starts 5 seconds faster if it is not relieable after that and i am and enduser which tries to make his F15 setup complete what it is not as shipped - so i like to see systemd trsutable work as sysvinit did over 40 years Also why do you want mysqld to start *before* syslog? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers and see here: http://0pointer.de/public/systemd-man/systemd.service.html If [type] set to simple (the default value) it is expected that the process configured with ExecStart= is the main process of the service. In this mode, if the process offers functionality to other processes on the system its communication channels should be installed before the daemon is started up (e.g. sockets set up by systemd, via socket activation), as systemd will immediately proceed starting follow-up units. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers so the After and Before is quite useless what should they do if it does not matter what you configure? i want mysqld before rsyslog because rsyslog-mysql is used believe me that i really know exactly why what order of every little piece of service is needed as it is on all machines i maintain "Type=simple" is suitable for servers only if they provide socket activation, because with this type is not possible to detect if the service is still starting or if it has fully started already. (In reply to comment #2) > and i am and enduser which tries to make his F15 setup complete what it is > not as shipped By making F15 complete you mean replacing _all_ SysV initscripts by systemd unit files? Then you are not just an end user, but also a developer. I recommend you to join the upstream systemd-devel mailing list and the #systemd IRC channel and discuss any questions you have about systemd there. Helping with conversions to native unit files is surely a welcome effort, but you need to know what you're doing and it's best to work with upstream. I am closing this bug as CANTFIX, because the described problems are not bugs in F15. They are caused by buggy custom unit files. |