Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
 2012-10-15 18:26:27.360 [info]   SCHEDULER-918  state=starting (at=2012-10-15 18:26:27.333)
 2012-10-15 18:26:27.361 [info]   SCHEDULER-987  Starting process: '/bin/sh' '-c' '"/tmp/schedule/sos.ABC"'
 2012-10-15 18:26:27.475 [info]   /tmp/schedule/sos.ABC: line 4: ./TDloadXXX: Permission denied
 2012-10-15 18:26:27.475 [info]   SCHEDULER-915  Process event
 2012-10-15 18:26:27.476 [ERROR]  SCHEDULER-280  Process terminated with exit code 126 (0x7E)

I noticed there is a SETUID setuid utility that could be used, I have looked through the FAQ, could you give us some information please as this could fix our issue?

Answer

SETUID The setuid utility is deprecated.

Display feature availability
EndingWithRelease1.11

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1565

There are some more There are, however, two other possible ways of accessing an object belonging to another user.a different user:

  • Use Agent instances

  • Use sudo in the JobScheduler job.

    • To access a file belonging to "other_user" use
      sudo -u other_user script_for_other_user.

    sh
    • sh 

    • Make sure that other_user doesn't

    need
    • require a password for sudo. This

    is done by editing the
    • can be achieved by adjusting the configuration from the sudoers file. This method has the advantage that it is extremely flexible - you can change the user more than once within a job. if sudo requires a

    sudo
    • password

    required
    • then you can

    call
    • use 
      echo "<password>" | sudo -S -u other_user script_for_other_user.sh