In some rare occasions following a host lock/unlock or force
reboot, there are two rpc.statd process one of which is a
runaway that floods daemon.log causing high CPU alarm. Based
on a few samples of startup sequence (success vs failure),
it is evident that the issue appeared each time mountnfs unit
had been loaded before rpc.statd process was started.
This change ensures nfscommon unit, which starts rpc.statd
and rpc.idmapd, is loaded before mountnfs unit.
Tests performed:
- installation (standard system)
- sanity (automated, repeats = 10)
Closes-Bug: 1794366
Change-Id: I6a916b9c3348338b0ab79fcec4f2cd5d04741499
Signed-off-by: Tee Ngo <Tee.Ngo@windriver.com>
d7d8b3cf06