#12258: [launch_daemon] increased boot time
-------------------------------------+----------------------------
Reporter: diver | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Servers/launch_daemon | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-------------------------------------+----------------------------
Comment (by mmlr):
I've added the system_time bin command which prints system_time() (the
uptime in microseconds) and a script for determining the "boot complete"
point in hrev49598. I'll also attach these to this ticket (for x86_gcc2)
as on older hrevs they will obviously not be available. The established
criterion is "all servers (and Tracker & Deskbar) are started and respond
to messages", which is probably as close as one can get to the definition
of a usable system. Note that this isn't super precise either as the used
waitfor has a generous 100ms delay loop when waiting, but it should be
reasonably close.
To take measurements, put the system_time binary and boot_time_logger.sh
script into {{{/boot/home/config/non-packaged/bin}}} and add the following
line to {{{/boot/home/config/settings/boot/UserBootScript}}}:
{{{
boot_time_logger.sh >> /boot/home/Desktop/boot_time.txt
}}}
After each reboot a new line should appear in that file on the desktop
telling the uptime after the script waited for a reply of all servers.
With the results we should be able to finally decide if this ticket can be
closed.
A side note regarding the shutdown problem: The launch_daemon is
definitely innocent in this case, as it doesn't change anything in that
regard. I have observed a regular crash in the BMediaRoster looper when
the media_server quits during shutdown, which is a recent regression. In
my configuration this does not prevent shutdown, but it might be different
depending on timing.
--
Ticket URL: <https://dev.haiku-os.org/ticket/12258#comment:28>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
