Timeout for process services is currently meaningless, although when
startup notification is implemented it will take on meaning. This is a
slightly cleaner fix than just forcing the timeout to 0 in the
constructor (since it can then still be later set to a value that won't
work).
event_loop.get_time(restart_interval_time, clock_type::MONOTONIC);
restart_interval_count = 0;
if (start_ps_process(exec_arg_parts, onstart_flags.starts_on_console)) {
- if (start_timeout != time_val(0,0)) {
+ // Note: we don't set a start timeout for PROCESS services.
+ if (start_timeout != time_val(0,0) && get_type() != service_type_t::PROCESS) {
restart_timer.arm_timer_rel(event_loop, start_timeout);
stop_timer_armed = true;
}
: base_process_service(sset, name, service_type_t::PROCESS, std::move(command), command_offsets,
depends_p)
{
- start_timeout = time_val(0,0);
}
~process_service() noexcept