on a clients TS-h765eU-8G-US I encountered a weird edge case that I though I would document because I spent the better part of an hour trying to figure this one out
cutting to it
so if you create a new user on the NAS then immediately delete that new user
the richacl process can hang and get stuck trying to apply permissions resulting in endless richacl crashes and background task notifications
the fix is relatively strait forward
ensure the ACLs are actually sane by running richacl -G and comparing it against known good
OR restore a snapshot that was taken prior to adding the new user
in the event of a stale record clearing the confs from
/tmp/richacl_progress.conf
/etc/config/richacl/richacl_*.config
will resolve the stuck notification and prevent the nas from respawning richacl and having it crash loop
the correct upstream fix is to make richacl track when its attempting to apply a ACL policy that isn’t valid and then abort cleanly
