Hide Forgot
Description of problem: Sometimes sendmail.service and sm-client.service are not shown in systemd-analyze plot. According to talk with mschmidt it could be caused by sendmail restart that is initiated from NetworkManager dispatcher script - it probably tricks systemd. Version-Release number of selected component (if applicable): systemd-37-11.fc16 How reproducible: Sometimes Steps to Reproduce: 1. Boot 2. systemd-analyze plot > boot.svg Actual results: sendmail.service and sm-client.service are not shown. Expected results: sendmail.service and sm-client.service are shown. Additional info: It is reproducible only on some machines, probably those where the NetworkManager script is triggered during boot.
(In reply to comment #0) > Description of problem: > Sometimes sendmail.service and sm-client.service are not shown in > systemd-analyze plot. According to talk with mschmidt it could be caused by > sendmail restart that is initiated from NetworkManager dispatcher script - it > probably tricks systemd. Yes. The dispatcher script does try-restart of sendmail. The dispatcher script can get executed after systemd has booted. The timestamps of sendmail.service will thus all be overwritten with new ones, and they will be outside of the boot window that 'systemd-analyze plot' renders. If we want systemd-analyze to show the original start of sendmail during boot, it must not depend on using the timestamps of the unit. I suppose we could rewrite it to read out the events from the journal.
I am not convinced we really should fix anything here. (well, maybe make sendmail watch network interfaces natively, if people insist on using sendmail)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Systemd has gained native bootchart integration which should land in f19/f20 feel free to reopen and or file a new bug against the release it lands in if this still an issue in that graph, Thanks