Sponsored Content
Top Forums Shell Programming and Scripting What does the following exec command do it is in the shell file? Post 302998604 by jim mcnamara on Sunday 4th of June 2017 08:42:08 PM
Old 06-04-2017
Hmm. Is the process run normally under a chrooted user? i.e., the user is in a chroot jail so the

Code:
/TTH_WORK_DIR/LOGS/

would exists for that user off the root directory.

I am assuming you executed this and found nothing:
Code:
find / -type d -name 'TTH_WORK_DIR'

And there are no links in the user's home directory by the same name.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

using the -exec command

linux redhat 8.0 I am getting accustomed to using the -exec command to get around my databse.. and use it to edit and update files..! is this more apllicable than jumping from one directory to the other.. I have set up the databse so that the inode #'s are accessable and can get me from one... (0 Replies)
Discussion started by: moxxx68
0 Replies

2. Shell Programming and Scripting

Help with exec command and file descriptors??

im having trouble with the comprehending the exec command and the use of file descriptors. given: #!/bin/sh exec 4>&1 exec 1>&2 exec 2>&4 exec 4>&- echo Hello would the standard output of this script be sent to STDOUT, STDERR or neither and why??? thanks for the help. (1 Reply)
Discussion started by: rfourn
1 Replies

3. Shell Programming and Scripting

how to use exec command in C shell

i have a script where i am reading some lines from a file into another file.. script works fine in bash.. #!/usr/bin/csh awk 'NR>20&&NR<32' try.sum | awk '{print $4 }' >io awk 'NR>20&&NR<32' try.sum | awk '{print $9 }' >io1 awk 'NR>20&&NR<32' try.sum | awk '{print $14 }'>io2 exec 10<io... (1 Reply)
Discussion started by: npatwardhan
1 Replies

4. Shell Programming and Scripting

Help with exec command and file descriptors II

Need to close files which descriptor number are larger than 9 in ksh. 'exec 10>&-' fails with 'ksh: 10: not found'. How do you specify file descriptors which occupies two or more digits in ksh script? Thanks, Masaki (2 Replies)
Discussion started by: masaki
2 Replies

5. Shell Programming and Scripting

Appending to a file using exec command

Hi, I need the data to be appended to the file using exec command in linux. I am able to add the data to a file using exec command but the file is getting overwritten. Above exec command is used to overwite in a file. When I use "exec >>& fileName", getting "syntax error near... (3 Replies)
Discussion started by: Anjan1
3 Replies

6. UNIX for Dummies Questions & Answers

Exec command

Hi can some one explain the following command , It would really help if some can really elloborate on what is happening out here export PATH | exec /bin/sh ./auto_approve :q P.S: This is the first time i am using exec ,so an elloboration what does it do and what is the use of the :q will be... (1 Reply)
Discussion started by: Sri3001
1 Replies

7. Shell Programming and Scripting

"exec" command. Stopoutput to file.

I have a script (ksh, Linux) which is about 500 lines and this is only a small requirement. Below is an example of my requirement. FunctionThis(){ echo "You are in this. Goes to log" } FunctionThat(){ echo "You are in That. Goes to log" } FunctionScreen(){ echo "You are in Screen.... (3 Replies)
Discussion started by: edidataguy
3 Replies

8. Shell Programming and Scripting

Linux find command seems to not transmit all the result to the '-exec command'

Hello. From a script, a command for a test is use : find /home/user_install -maxdepth 1 -type f -newer /tmp/000_skel_file_deb ! -newer /tmp/000_skel_file_end -name '.bashrc' -o -name '.profile' -o -name '.gtkrc-2.0' -o -name '.i18n' -o -name '.inputrc' Tha command... (3 Replies)
Discussion started by: jcdole
3 Replies
cvsd-buildroot(8)					      System Manager's Manual						 cvsd-buildroot(8)

NAME
cvsd-buildroot - create a chrooted directory structure for use in cvsd. SYNOPSIS
cvsd-buildroot DIRECTORY DESCRIPTION
cvsd-buildroot creates and populates a directory that can be used as a chroot jail for running cvsd (see cvsd(8) ) in. This script should be run as the root user since the creation of devices and the changing of ownership and permissions require this. The script gives warnings about files that it's not expecting. cvsd-buildroot creates the following directory structure: /bin This directory is populated with the cvs binary that is found on the system. /lib This directory is populated with all the libraries that are required for running programs in the /bin directory as well as some predefined required libraries that are present on the system. /dev Here null and zero devices are created. /etc In this directory a passwd file is created that is used for matching user id's with usernames. The root and cvsd user are added to this file if they're not there yet. The passwd file is checked for consistency with the system /etc/passwd to prevent mistakes. The passwd file is also populated with users referenced in the repository directories. Note that no password data from /etc/passwd or any other file is stored in the generated passwd file, all password entries are set to 'x'. /usr Here symbolic links are placed to /bin and /lib for some common library and binary directories found on the system. This is done for systems that have hard-coded paths for libraries. /libexec and /usr/libexec Symbolic links for these directories are created if they are present on the system. /tmp This directory is cleaned out on systems that have tmpreaper. After the directories are created and populated ownership and rights are set to a reasonable value (root:root,umask=022). OPTIONS
cvsd-buildroot takes one argument, namely a directory in which the chroot jail will be created. The directory should be specified with an absolute path. NOTES
Creating a chroot environment is a terribly non-portable thing to do and therefore you may experience problems with missing libraries and system files. For more information see the FAQ and the README. If you have to install libraries or perform actions not covered by cvsd-buildroot please report your findings to <cvsd-users@lists.arthurdejong.org>. Rerunning cvsd-buildroot after you have created your repository is advised since the repositories are checked for references to userid's and lockfile directories. SEE ALSO
cvsd(8) README FAQ AUTHOR
Arthur de Jong <arthur@arthurdejong.org>. Version 1.0.24 Jun 2012 cvsd-buildroot(8)
All times are GMT -4. The time now is 01:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy