Skip to main content
added 99 characters in body
Source Link
Cory Klein
  • 1.4k
  • 1
  • 16
  • 24

The asker mentions LaunchAgents a couple of times and @klanomath's answer is correct: in this case a LaunchDaemon is probably the appropriate approach.

However for Googlers that are trying to give a LaunchAgent elevated sudo/root privileges, I recommend checking out either klanomath's answer or Cory Klein'sthis answer on this question about LaunchAgents.

It describes a method of having selectively elevated privileges for the user and command you're running, allowing launchctl to run sudo without an interactive password prompt.

The asker mentions LaunchAgents a couple of times and @klanomath's answer is correct: in this case a LaunchDaemon is probably the appropriate approach.

However for Googlers that are trying to give a LaunchAgent elevated sudo/root privileges, I recommend checking out either klanomath's answer or Cory Klein's answer on this question about LaunchAgents.

The asker mentions LaunchAgents a couple of times and @klanomath's answer is correct: in this case a LaunchDaemon is probably the appropriate approach.

However for Googlers that are trying to give a LaunchAgent elevated sudo/root privileges, I recommend checking out or this answer on this question about LaunchAgents.

It describes a method of having selectively elevated privileges for the user and command you're running, allowing launchctl to run sudo without an interactive password prompt.

Source Link
Cory Klein
  • 1.4k
  • 1
  • 16
  • 24

The asker mentions LaunchAgents a couple of times and @klanomath's answer is correct: in this case a LaunchDaemon is probably the appropriate approach.

However for Googlers that are trying to give a LaunchAgent elevated sudo/root privileges, I recommend checking out either klanomath's answer or Cory Klein's answer on this question about LaunchAgents.