09-20-2007
The last I knew, the ./ means run the command from the current directory. I don't think it matters the shell.
You could get away with not using that if you are sitting in the directory where the path is or have that path setup in your environment.
I suggest to check your environment path and see if the directory where the script resides is still in your path and that no other path's higher have that same script name.
9 More Discussions You Might Find Interesting
1. Linux
Hi All,
I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that.
Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies
2. Shell Programming and Scripting
Hello people,
I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now.
Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies
3. IP Networking
I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load.
Error for wireless request "Set Mode" (8B06) :
SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies
4. Shell Programming and Scripting
Hi,
I have the following segment of a script which is supposed to prompt a user for password and then capture the password entered by the user.
The function is called in by another script and used to work without issue, the problem is that recently the script is not waiting for the user to... (3 Replies)
Discussion started by: belalr
3 Replies
5. UNIX for Dummies Questions & Answers
I Was able to ssh into the AIX box. now i cannot When I run the command to start it it comes back that is was started, but still does not work. Here is a shot i what i see
# server:/> lslpp -l | grep ssh
openssh.base.client 4.3.0.5201 COMMITTED Open Secure Shell Commands
... (2 Replies)
Discussion started by: fierfek
2 Replies
6. Shell Programming and Scripting
I am trying to automate a script where I need to use pbrun /bin/su but for some reason it is not passing thru the pbrun as my code below.
. ~/.bash_profile
pbrun /bin/su - content
c h 1
hpsvn up file path
I am executing this from an external .sh file that is pointing to this scripts file... (14 Replies)
Discussion started by: jorgejac
14 Replies
7. Shell Programming and Scripting
Some question about the usage of shell scripts:
1.) Are the commands of the base shell scripts a subset of bash commands?
2.) Assume I got a long, long script WITHOUT the first line.
How can I find out if the script was originally designed für "sh" or "bash"?
3.) How can I check a given... (3 Replies)
Discussion started by: pstein
3 Replies
8. AIX
I have a serial printer connected to a 16 port ran. All of a sudden my printer stopped working and not sure how to get it back. Can anyone help pint me in the write direction?
lsdev -Cc printer gives me the following.
lp0 Defined 0A-08-11-00 Other serial printer
lp1 Defined 0A-08-11-03... (3 Replies)
Discussion started by: Gmanx
3 Replies
9. Solaris
after a new patch set on the 14th. I noticed that mailx stopped working, as far a I can tell that is the only thing that changed.
solaris 10 OS
it seems everything is the same, sendmail seems to be running
root@server # ps -ef | grep -i sendmail
smmsp 687 1 0 10:42:25 ? ... (0 Replies)
Discussion started by: goya
0 Replies
rmdir(2) System Calls Manual rmdir(2)
NAME
rmdir() - remove a directory file
SYNOPSIS
DESCRIPTION
The system call removes a directory file whose name is given by path. The directory must be empty (except for the files and before it can
be removed.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
If fails, is set to one of the following values.
[EACCES] A component of the path prefix denies search permission.
[EACCES] Write permission is denied on the directory containing the link to be removed.
[EACCES] The process does not have read/write access permission to the parent directory.
[EBUSY] The directory to be removed is the mount point for a mounted file system.
[EBUSY] The path is the current working directory.
[EEXIST] The named directory is not empty. It contains files other than and
[EFAULT] path points outside the process's allocated address space. The reliable detection of this error is implementation-
dependent.
[ELOOP] Too many symbolic links were encountered in translating the path name.
[ENAMETOOLONG] The length of the specified path name exceeds bytes, or the length of a component of the path name exceeds bytes
while is in effect.
[ENOENT] The named file does not exist.
[ENOTDIR] A component of the path is not a directory.
[EPERM] The directory containing the directory to be removed has the sticky bit set and neither the containing directory nor
the directory to be removed are owned by the effective user ID.
[EROFS] The directory entry to be removed resides on a read-only file system.
AUTHOR
was developed by the University of California, Berkeley and HP.
SEE ALSO
mkdir(2), unlink(2), remove(3C), privileges(5).
STANDARDS CONFORMANCE
rmdir(2)