Starting the openafs-client service is an intensive operation as it walks the cache registering various things. We've seen on our production ARM64 mirror this can take longer than the 1:30 default timeout. This is a fatal issue, as the module will try to unload while afsd is still spinning and working resulting in completely corrupt kernel state. This is about double the longest time we've seen, so should give plenty of overhead. Change-Id: I37186494b9afd72eab3a092279579f1a5fa5d22c
164 B
164 B