12-11-2007
Quote:
Originally Posted by
jim mcnamara
The first one is correct if example.sh is in the current working directory.
and assuming that the file is executable and has a #! line at the beginning
9 More Discussions You Might Find Interesting
1. Solaris
Hello everybody,
I am having two machines. I am using g++v2.95
When I do the build,the size of output file on both machines differ. I am not able to find what can be the problem. Both the machines are solaris 5.6
The command is :
g++ -c -g -I./ -I../../../include -I/usr/local/include/g++-3... (1 Reply)
Discussion started by: manishs13
1 Replies
2. Shell Programming and Scripting
it is a simple problem, but I am totally new to shell programming
There are 2 files. I have to print the 5 five lines which are different.
I appreciate any help.
10x. (2 Replies)
Discussion started by: atticus
2 Replies
3. UNIX for Advanced & Expert Users
I always find that the pid I get from:
/var/run/syslog-ng.pid
and
ps -ef |grep syslog-ng
are different.
this also happens on other pids. why?
If I am going to kill a process, which pid should I use? (1 Reply)
Discussion started by: fredao
1 Replies
4. Shell Programming and Scripting
Hi.
On my system there is a script which making backup to ftp site. But it leaves copy of files on local machine. Then i go to Midnight Commander and check manually with MC features - i open ftp directory and copy files <if size differs>.
So, how can i do the last thing in shell or other... (1 Reply)
Discussion started by: kukuruku
1 Replies
5. Shell Programming and Scripting
I have the following script (MyScript):
#!/bin/sh
ps U erv | grep -v grep | grep -F "/usr/bin/collect -o 101"
echo "Result: $?"
When executed from the command line, I get
... (the line containing /usr/bin/collect -o 101)
Result: 0
(which is correct since collect is running)
When I... (4 Replies)
Discussion started by: lost_neko
4 Replies
6. Programming
hello all,
i want to know if there is any difference in working and syntax declaration of abstract class in Java and C++. (1 Reply)
Discussion started by: haravivar
1 Replies
7. UNIX for Advanced & Expert Users
I tried several times to get answer to the below problem. Someone can please help me?
$ cat p1.sh
#!/bin/sh
`./c1.sh &`
while # indefinite loop
do
x=5;
done
$ cat c1.sh # sleep for 10 sec and exit
#!/bin/sh
sleep 10;
Execute P1 as ./p1 &
$ ps -eaf | grep c1... (1 Reply)
Discussion started by: alexalex1
1 Replies
8. Shell Programming and Scripting
Hi All,
I have a very basic query for 'echo $$' command.
When I am executing echo $$ on console then it is giving different output than the execution of echo $$ in a script.
Console Output:
-------------------------
bash-3.2$ echo $$
15610
bash-3.2$
In Script:... (3 Replies)
Discussion started by: manishdivs
3 Replies
9. Shell Programming and Scripting
I get a different output when i manually run the .sh script and when it is run by a cron job. Please help me ..
TMP1="/lhome/bbuser/script/wslog/sar.t1"
TMP2="/lhome/bbuser/script/wslog/sar.t2"
TMP3="/lhome/bbuser/script/wslog/sar.t3"
OUTPUT="/lhome/bbuser/script/wslog/sar.out"... (8 Replies)
Discussion started by: nithinankam
8 Replies
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() function 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() function 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, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
chdir() 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 {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} 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] path points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
fchdir() 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.
[EPERM] The argument fd references a directory which is not at or below the current process's root directory.
SEE ALSO
chroot(2)
STANDARDS
The chdir() function conforms to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The fchdir() function call appeared in 4.2BSD.
BSD
December 11, 1993 BSD