aeae87d1b5
#### Why I did it Since we will have multiple `dhcrelay` processes if there exists different VLANs in the table `VLAN_INTERFACE` of `CONIFG_DB`, we should use unique service name for each `dhcrelay` process in Monit configuration file. Otherwise, Monit service will fail to work. #### How I did it I append the VLAN name to the end of each service name such that they are unique. Signed-off-by: Yong Zhao <yozhao@microsoft.com> |
||
|---|---|---|
| .. | ||
| docker-base | ||
| docker-base-stretch | ||
| docker-basic_router | ||
| docker-config-engine | ||
| docker-config-engine-stretch | ||
| docker-database | ||
| docker-dhcp-relay | ||
| docker-fpm-frr | ||
| docker-fpm-gobgp | ||
| docker-fpm-quagga | ||
| docker-lldp-sv2 | ||
| docker-nat | ||
| docker-orchagent | ||
| docker-platform-monitor | ||
| docker-ptf | ||
| docker-ptf-saithrift | ||
| docker-router-advertiser | ||
| docker-sflow | ||
| docker-snmp-sv2 | ||
| docker-sonic-mgmt | ||
| docker-sonic-mgmt-framework | ||
| docker-sonic-restapi | ||
| docker-sonic-telemetry | ||
| docker-teamd | ||
| dockerfile-macros.j2 | ||