Summary: | ugidfw starts before late mount of nfs causing permissions errors on /var/run/nslcd | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Dan Langille <dvl> | ||||
Component: | conf | Assignee: | freebsd-rc (Nobody) <rc> | ||||
Status: | New --- | ||||||
Severity: | Affects Some People | CC: | andrew, grahamperrin, joris.dedieu | ||||
Priority: | --- | Keywords: | regression | ||||
Version: | 13.0-RELEASE | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Dan Langille
2021-06-16 19:58:16 UTC
Something that occurs to me is that there might be a use for some way to specify additional dependency order constraints for services in rc.conf to avoid having to modify rc.d files. In the specific case of ugidfw, it's not clear whether putting it after mountlate in the rcorder would be the right fix for all circumstances (though it'd still be a vast improvement over the current case where ugidfw can run at literally any point between FILESYSTEMS and LOGIN). (The "irc guru" referred to in the original report was me) ^Triage: needs to be examined by someone more familiar with /etc/rc.d/ugidfw than I am. At $WORK we are still manually hacking ugidfw and adding latestart. Created attachment 243198 [details]
Change ugidfw start order
Hi,
We have same issues with ldap based users. Boot hangs until ldap timeout because ugidfw starts before network
Maybe changing REQUIRE: FILESYSTEMS into REQUIRE: NETWORKING is the simplest way to fix this issue.
Regards
Joris
|