Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 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 Commented Oct 12, 2018 at 6:09
  • @YashGandhi I'm talking about your current working directory when you run the command, not the directory that it's in. Commented Oct 12, 2018 at 13:20
  • 2
    Wow, this sucks REALLY bad. How is it possible that such a core tool has this issue? Commented Sep 20, 2019 at 7:26
  • @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. Commented Sep 20, 2019 at 12:24