Sponsored Content
Full Discussion: Unix Process
Operating Systems Linux Red Hat Unix Process Post 302444748 by mark54g on Thursday 12th of August 2010 04:57:04 PM
Old 08-12-2010
You should set the binary to be SUID to the user you wish it to run as. Alternately have your script run an su -c <user>
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Process Failed

Im having this problem ever since im Using Unix. Please help.Im using Linux Red Hat 7.0. 2.2.6. My Problem is. Whenever i close my unix before the system goes to Halt mode and stoping all md device, this Process shows me as fail. : Saving Mixer settings modprobe: modprobe: can't locate module... (1 Reply)
Discussion started by: killerserv
1 Replies

2. Programming

Unix Process

I have successfully opened /dev/table/proc file and read processes pids and its details from it, but I am unable to have programatic knowledge of how to access process CMD or its corresponding name. Kindly do guide me out on the said request for which I will be very thankfull. (3 Replies)
Discussion started by: S.P.Prasad
3 Replies

3. UNIX for Dummies Questions & Answers

UNIX Process Suspend

Hi, I have this doubt.... When some program is running and if we press CTRL+Z...it is suspended... what should we do to continue its execution I know that KILL can be used to completely terminate the process....but is there any way to continue... Thanks (3 Replies)
Discussion started by: proton
3 Replies

4. Programming

How to get process name from process id in all Unix platforms?

Hi, i need to find the process name using the process id in C. This has to be done in HP, AIX, Solaris & Linux?? How can this be done? Is there any common solution to all platforms? On linux i have heard that /proc/<pid>/cmdline can be used. Is there a structure available to read this? ... (3 Replies)
Discussion started by: molu
3 Replies

5. UNIX for Dummies Questions & Answers

Unix Process

Hi does unix keep track of the processes or programs it ran. can i check when my program last ran on the system. any suggestions are welocme. -- logs made by the program it self are missing. Regards Debadatta (4 Replies)
Discussion started by: mishra.dd
4 Replies

6. Shell Programming and Scripting

Help required on process in unix

What are some ways to tell if a given file is presently being used by a process? How can you tell what sort of access the process has to the file (read from, written to, filehandle held open, etc)? Can more than one process access the file at the same time? (2 Replies)
Discussion started by: choco4202002
2 Replies

7. Shell Programming and Scripting

UniX Process not getting logout.

Hi, We have UNIX menu. when we exit the menu the processes are not getting log out. please suggest me how to log out the process after exit from the UNIX Menu. Regards, laknar. (3 Replies)
Discussion started by: laknar
3 Replies

8. Shell Programming and Scripting

Shell Script to Kill Process(number of process) Unix/Solaris

Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies

9. UNIX for Dummies Questions & Answers

Unix Process

Hi , i scheduled jobs in crontab with dependency. some child process id killed without manual intervention or script . please add you thoughts how process id killed automatically. (1 Reply)
Discussion started by: challamsomu
1 Replies

10. UNIX for Dummies Questions & Answers

unix process

I have to create a parent process that receives n arguments, arg1, arg2 ... argn. The parent creates n son processes. Each one of these will read a text file argi and will print the pair of lines from the file in reversed order. Can anyone help me with this problem, please? (3 Replies)
Discussion started by: oana06
3 Replies
EXECVE(2)						     Linux Programmer's Manual							 EXECVE(2)

NAME
execve - execute program SYNOPSIS
#include <unistd.h> int execve(const char *filename, char *const argv [], char *const envp[]); DESCRIPTION
execve() executes the program pointed to by filename. filename must be either a binary executable, or a script starting with a line of the form "#! interpreter [arg]". In the latter case, the interpreter must be a valid pathname for an executable which is not itself a script, which will be invoked as interpreter [arg] filename. argv is an array of argument strings passed to the new program. envp is an array of strings, conventionally of the form key=value, which are passed as environment to the new program. Both, argv and envp must be terminated by a null pointer. The argument vector and environ- ment can be accessed by the called program's main function, when it is defined as int main(int argc, char *argv[], char *envp[]). execve() does not return on success, and the text, data, bss, and stack of the calling process are overwritten by that of the program loaded. The program invoked inherits the calling process's PID, and any open file descriptors that are not set to close on exec. Signals pending on the calling process are cleared. Any signals set to be caught by the calling process are reset to their default behaviour. The SIGCHLD signal (when set to SIG_IGN) may or may not be reset to SIG_DFL. If the current program is being ptraced, a SIGTRAP is sent to it after a successful execve(). If the set-uid bit is set on the program file pointed to by filename the effective user ID of the calling process is changed to that of the owner of the program file. Similarly, when the set-gid bit of the program file is set the effective group ID of the calling process is set to the group of the program file. If the executable is an a.out dynamically-linked binary executable containing shared-library stubs, the Linux dynamic linker ld.so(8) is called at the start of execution to bring needed shared libraries into core and link the executable with them. If the executable is a dynamically-linked ELF executable, the interpreter named in the PT_INTERP segment is used to load the needed shared libraries. This interpreter is typically /lib/ld-linux.so.1 for binaries linked with the Linux libc version 5, or /lib/ld-linux.so.2 for binaries linked with the GNU libc version 2. RETURN VALUE
On success, execve() does not return, on error -1 is returned, and errno is set appropriately. ERRORS
EACCES The file or a script interpreter is not a regular file. EACCES Execute permission is denied for the file or a script or ELF interpreter. EACCES The file system is mounted noexec. EPERM The file system is mounted nosuid, the user is not the superuser, and the file has an SUID or SGID bit set. EPERM The process is being traced, the user is not the superuser and the file has an SUID or SGID bit set. E2BIG The argument list is too big. ENOEXEC An executable is not in a recognised format, is for the wrong architecture, or has some other format error that means it cannot be executed. EFAULT filename points outside your accessible address space. ENAMETOOLONG filename is too long. ENOENT The file filename or a script or ELF interpreter does not exist, or a shared library needed for file or interpreter cannot be found. ENOMEM Insufficient kernel memory was available. ENOTDIR A component of the path prefix of filename or a script or ELF interpreter is not a directory. EACCES Search permission is denied on a component of the path prefix of filename or the name of a script interpreter. ELOOP Too many symbolic links were encountered in resolving filename or the name of a script or ELF interpreter. ETXTBSY Executable was open for writing by one or more processes. EIO An I/O error occurred. ENFILE The limit on the total number of files open on the system has been reached. EMFILE The process has the maximum number of files open. EINVAL An ELF executable had more than one PT_INTERP segment (i.e., tried to name more than one interpreter). EISDIR An ELF interpreter was a directory. ELIBBAD An ELF interpreter was not in a recognised format. CONFORMING TO
SVr4, SVID, X/OPEN, BSD 4.3. POSIX does not document the #! behavior but is otherwise compatible. SVr4 documents additional error condi- tions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL, EIS- DIR or ELIBBAD error conditions. NOTES
SUID and SGID processes can not be ptrace()d. Linux ignores the SUID and SGID bits on scripts. The result of mounting a filesystem nosuid vary between Linux kernel versions: some will refuse execution of SUID/SGID executables when this would give the user powers she did not have already (and return EPERM), some will just ignore the SUID/SGID bits and exec success- fully. A maximum line length of 127 characters is allowed for the first line in a #! executable shell script. SEE ALSO
chmod(2), fork(2), execl(3), environ(5), ld.so(8) Linux 2.0.30 1997-09-03 EXECVE(2)
All times are GMT -4. The time now is 09:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy