fa1e364f54
To optimize stop on warm boot, added kill for containers Use service "kill" in the shutdown path for fast and warm reboot. For all other reload methods, service "stop" is used. This is done to save time in shutdown path, and to overall improve the time spent in warm and fast reload. How - Use service_mgmt.sh to trigger common logic to initiate kill (fast/warm) or stop (cold) for database.sh, radv.sh, snmp.sh, telemetry.sh, mgmt-framework.sh Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>, Vaibhav H D <vaibhav.dixit@microsoft.com>
18 lines
473 B
Django/Jinja
18 lines
473 B
Django/Jinja
[Unit]
|
|
Description=Telemetry container
|
|
Requires=database.service
|
|
After=database.service swss.service syncd.service
|
|
Before=ntp-config.service
|
|
BindsTo=sonic.target
|
|
After=sonic.target
|
|
StartLimitIntervalSec=1200
|
|
StartLimitBurst=3
|
|
|
|
[Service]
|
|
User={{ sonicadmin_user }}
|
|
ExecStartPre=/usr/local/bin/{{docker_container_name}}.sh start
|
|
ExecStart=/usr/local/bin/{{docker_container_name}}.sh wait
|
|
ExecStop=/usr/local/bin/{{docker_container_name}}.sh stop
|
|
Restart=always
|
|
RestartSec=30
|