Timeline for find: failed to restore initial working directory: Permission denied
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2019 at 12:24 | comment | added | Joseph Sible-Reinstate Monica | @AFP_555 Is this really a big issue? Why do you need to run find from a directory that you don't have permission to enter? If it's really a big deal for some reason, you could see about sending upstream patches to make it use the *at functions instead. | |
| Sep 20, 2019 at 7:26 | comment | added | AFP_555 | Wow, this sucks REALLY bad. How is it possible that such a core tool has this issue? | |
| Oct 12, 2018 at 13:20 | comment | added | Joseph Sible-Reinstate Monica | @YashGandhi I'm talking about your current working directory when you run the command, not the directory that it's in. | |
| Oct 12, 2018 at 6:09 | comment | added | Yash Gandhi | If you're talking about the command "sudo -u" in /etc/cron.weekly/ the shell file has the owner root with 777 access. So jboss already has access to that path | |
| Oct 12, 2018 at 2:41 | history | answered | Joseph Sible-Reinstate Monica | CC BY-SA 4.0 |