11-10-2008
chroot is not what you want, it changes the / path to be the named dir, so any subsequent calls will have that as their / path - not a good idea
chdir() is what you need
man 2 chdir will give you information on chdir (on a linux machine anyway)
10 More Discussions You Might Find Interesting
1. Programming
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
Discussion started by: tejbuch
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
Ho do I differentiate system call from library call?
for example if I am using chmod , how do I find out if it is a system call or library call?
Thanks
Muru (2 Replies)
Discussion started by: muru
2 Replies
3. Shell Programming and Scripting
HI,
if I have a tarfile called pmapdata.tar that contains
tar -tvf pmapdata.tar
-rw-r--r-- 0/0 21 Oct 15 11:00 2009 /var/tmp/pmapdata/pmap4628.txt
-rw-r--r-- 0/0 21 Oct 14 20:00 2009 /var/tmp/pmapdata/pmap23752.txt
-rw-r--r-- 0/0 1625 Oct 13 20:00 2009... (1 Reply)
Discussion started by: borderblaster
1 Replies
4. Shell Programming and Scripting
Hi every one,
i have to dot pc files. One have main function but one dont have.I have to call dot pc file using system () cmd.File is being call have main function.Please let me know how i can call .pc file with two arguments from other dot pc file.I want some thing like
sprintf(buf,... (1 Reply)
Discussion started by: goraya430
1 Replies
5. Programming
Hi every one,
i have to dot pc files. One have main function but one dont have.I have to call dot pc file using system () cmd.File is being call have main function.Please let me know how i can call .pc file with two arguments from other dot pc file.I want some thing like sprintf(buf, "ss_xxx.pc... (4 Replies)
Discussion started by: goraya430
4 Replies
6. Shell Programming and Scripting
Hi All,
I have a script(sample.sh) displaying the output of "dd" command. Now i am using this script in system() call as,
system("sh sample.sh") in an application file.
I want the output of system("sh sample.sh") in the application file itself.
How can i get it?
Many thnaks.... (9 Replies)
Discussion started by: amio
9 Replies
7. Shell Programming and Scripting
Hello experts,
I have a perl script which looks for the ARGV and then loads the data as per it.
Example.
#Checking the server to connect
if ($ARGV eq 'QA')
{
$ENV{"ORACLE_HOME"} = "/oracle/product/11.2.0";
$ENV{"PATH"} = "$ENV{'PATH'}:/oracle/product/11.2.0/bin";
... (1 Reply)
Discussion started by: msrahman
1 Replies
8. Programming
hi everyone
i wrote a system call and compiled the kernel succesfully...
my system call is in a file in the kernel folder named my_syscall1.c (kernel/my_syscall1.c)
the header file for this system call i added it in the folder include like this include/my_syscall1/my_syscall1.h
my problem is... (2 Replies)
Discussion started by: demis87
2 Replies
9. Shell Programming and Scripting
Hello,
Recently, I've started with shell scripting, and decided to write a script for my system backup using tar. When I was dealing with tar execution inside shell script I found this, inside shell we have the following code:
tar $TAR_PARAMS $ARCHIVE_FILE $EXCLUDE $BACKUP_STARTwith... (6 Replies)
Discussion started by: ilnar
6 Replies
10. Shell Programming and Scripting
Hi all,
I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to... (1 Reply)
Discussion started by: bashnewbee
1 Replies
LEARN ABOUT DEBIAN
fchdir
CHDIR(2) BSD System Calls Manual CHDIR(2)
NAME
chdir, fchdir -- change current working directory
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
chdir(const char *path);
int
fchdir(int fd);
DESCRIPTION
The path argument points to the pathname of a directory. The chdir() system call causes the named directory to become the current working
directory, that is, the starting point for path searches of pathnames not beginning with a slash, '/'.
The fchdir() system call causes the directory referenced by fd to become the current working directory, the starting point for path searches
of pathnames not beginning with a slash, '/'.
In order for a directory to become the current directory, a process must have execute (search) access to the directory.
RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the
error.
ERRORS
The chdir() system call will fail and the current working directory will be unchanged if one or more of the following are true:
[ENOTDIR] A component of the path prefix is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
[ENOENT] The named directory does not exist.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EACCES] Search permission is denied for any component of the path name.
[EFAULT] The path argument points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
The fchdir() system call will fail and the current working directory will be unchanged if one or more of the following are true:
[EACCES] Search permission is denied for the directory referenced by the file descriptor.
[ENOTDIR] The file descriptor does not reference a directory.
[EBADF] The argument fd is not a valid file descriptor.
SEE ALSO
chroot(2)
STANDARDS
The chdir() system call is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The chdir() system call appeared in Version 7 AT&T UNIX. The fchdir() system call appeared in 4.2BSD.
BSD
December 11, 1993 BSD