On 3/14/19 4:04 PM, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > We really don't want the xfs_scrub_all timer triggering while the system > is booting up because not all the mounts will have finished, networking > might not be up for reporting, and slowing down bootup annoys people. > Therefore, delay the xfs_scrub_all service's activation until after the > system has started all the big pieces it's going to start. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> <mumble handwave systemd mumble> what happens if you state an After requirement for something that doesn't exist on the box? Is it just ignored? (he asks, after looking for what connman.service is and finds that it's not ubiquitous ...) > --- > scrub/xfs_scrub_all.service.in | 1 + > 1 file changed, 1 insertion(+) > > > diff --git a/scrub/xfs_scrub_all.service.in b/scrub/xfs_scrub_all.service.in > index 66f82fc7..b1b80da4 100644 > --- a/scrub/xfs_scrub_all.service.in > +++ b/scrub/xfs_scrub_all.service.in > @@ -2,6 +2,7 @@ > Description=Online XFS Metadata Check for All Filesystems > ConditionACPower=true > Documentation=man:xfs_scrub_all(8) > +After=paths.target multi-user.target network.target network-online.target systemd-networkd.service NetworkManager.service connman.service > > [Service] > Type=oneshot >
