Sponsored Content
Top Forums Shell Programming and Scripting Following Symlinks to Actual Script Post 302351466 by Scrutinizer on Tuesday 8th of September 2009 03:52:31 PM
Old 09-08-2009
This perhaps?
Code:
#!/bin/ksh
dir=$(pwd -P)

or do you mean the directory the scripts itself is located in?
Code:
#!/bin/ksh
dir=$(cd ${0%/*};pwd -P)


Last edited by Scrutinizer; 09-08-2009 at 05:07 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

search and replace symlinks

Hello All, Assuming i have a thousand symlinks under directory /mydir (and its sub-dir) such as: mysymlink1 -> ../../../myfoo/mysymlink1 mysymlink2 -> ../../../myfoo/mysymlink2 How can I search the string "myfoo" and replaced with "yourfoo" such that after the operation is complete the... (2 Replies)
Discussion started by: nixrock
2 Replies

2. Shell Programming and Scripting

Nested Symlinks?

Please don't laugh or call me a fool... I'm trying to set up a script that will go through my Music File directory and generate a set of symbolic links in a directory called "What's New". Within that directory there will be a "30 Days", "3 Months", "6 Months" and "A Year" directories. Within... (0 Replies)
Discussion started by: deckard
0 Replies

3. UNIX for Dummies Questions & Answers

Symlinks

Given a filename, is it possible to know haow many symbolic links are pointing to it? How can I tell? (1 Reply)
Discussion started by: ct1977
1 Replies

4. UNIX for Dummies Questions & Answers

tar symlinks: relative vs absolute

I create the tar file from / like so: tar cEhf name.tar usr/us And this creates the tar with the links intact. The problem is that this tar is going to be used for testing, so we want the links to point to the files in the tar. But when I extract the tar into /tmp, I get /tmp/usr/us/... as I... (2 Replies)
Discussion started by: TreeMan
2 Replies

5. Shell Programming and Scripting

Shell script that will compare two config files and produce 2 outputs 1)actual config file 2)report

Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated. script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made. OS :Susi linux ver 10.3. ... (4 Replies)
Discussion started by: muraliinfy04
4 Replies

6. Slackware

Context dependent symlinks

Ive got multiple PCs, sharing an NFS mounted home dir. For certain apps I would like to keep the config files host specific. Easy solution is to create symlinks to local folders for configs. Ideally I would still want the .config files to reside in the user home folder. Is it possible to... (2 Replies)
Discussion started by: agentrnge
2 Replies

7. Shell Programming and Scripting

Look for, backup and delete symlinks

Hi, My first post here: Was looking if someone can help enhancing my code. I am limited to sh or ash shell (android / busybox) I made a script to look for busybox symlinks, backup them and delete them I have these questions about the below code: - busybox tar do not has the options... (2 Replies)
Discussion started by: Phil3759
2 Replies

8. Shell Programming and Scripting

Find + Symlinks = me confused

So i have read the man pages a few time. Searched google but I am not quite sure i understand all the lingo. What i want to do is list all files on / except i dont want any symlinks (because if I am searching / I will find the "true" file...correct?) So there is the -P, -H, and '-type l'... (2 Replies)
Discussion started by: nitrobass24
2 Replies

9. Shell Programming and Scripting

Actual SQL instead of using a file from within a shell script

I am very noobish to UNIX, our guy is on vacation so I am trying to take up some slack while he is away. Typically when we use sql from within a shell script, we do so from a file containing the sql. Example: $ORACLE_HOME/bin/sqlplus $ORA_DBCU/$ORA_DBCP @${cron_dir}/${report_file}.sql ... (10 Replies)
Discussion started by: biobill
10 Replies

10. Shell Programming and Scripting

Rsync move with symlinks

Hi, I use rsync to move from source to target, but there are cases that I need to exclude: Suppose in my file system, I have a soft link ~/data -> /media/volgrp/data. Under data folder, there is a file hello.txt. After moving command "rsync --remove-source-files -aH --force ~/data/... (3 Replies)
Discussion started by: huangyingw
3 Replies
cd(1)								   User Commands							     cd(1)

NAME
cd, chdir, pushd, popd, dirs - change working directory SYNOPSIS
/usr/bin/cd [directory] sh cd [argument] chdir [argument] csh cd [dir] chdir [dir] pushd [+n | dir] popd [+n] dirs [-l] ksh, ksh93 cd [-L] [-P] [arg] cd old new DESCRIPTION
/usr/bin/cd The /usr/bin/cd utility changes the current directory in the context of the cd utility only. This is in contrast to the version built into the shell. /usr/bin/cd has no effect on the invoking process but can be used to determine whether or not a given directory can be set as the current directory. sh The Bourne shell built-in cd changes the current directory to argument. The shell parameter HOME is the default argument. The shell parame- ter CDPATH defines the search path for the directory containing argument. Alternative directory names are separated by a colon (:). The default path is <null> (specifying the current directory). The current directory is specified by a null path name, which can appear immedi- ately after the equal sign or between the colon delimiters anywhere else in the path list. If argument begins with `/', `.', or `..', the search path is not used. Otherwise, each directory in the path is searched for argument. cd must have execute (search) permission in argu- ment. Because a new process is created to execute each command, cd would be ineffective if it were written as a normal command; therefore, it is recognized by and is internal to the shell. (See pwd(1), sh(1), and chdir(2)). chdir is just another way to call cd. csh If dir is not specified, the C shell built-in cd uses the value of shell parameter HOME as the new working directory. If dir specifies a complete path starting with `/', `.', or `..', dir becomes the new working directory. If neither case applies, cd tries to find the desig- nated directory relative to one of the paths specified by the CDPATH shell variable. CDPATH has the same syntax as, and similar semantics to, the PATH shell variable. cd must have execute (search) permission in dir. Because a new process is created to execute each command, cd would be ineffective if it were written as a normal command; therefore, it is recognized by and is internal to the C-shell. (See pwd(1), sh(1), and chdir(2)). chdir changes the shell's working directory to directory dir. If no argument is given, change to the home directory of the user. If dir is a relative pathname not found in the current directory, check for it in those directories listed in the cdpath variable. If dir is the name of a shell variable whose value starts with a /, change to the directory named by that value. pushd pushes a directory onto the directory stack. With no arguments, exchange the top two elements. +n Rotate the n'th entry to the top of the stack and cd to it. dir Push the current working directory onto the stack and change to dir. popd pops the directory stack and cd to the new top directory. The elements of the directory stack are numbered from 0 starting at the top. +n Discard the n'th entry in the stack. dirs prints the directory stack, most recent to the left; the first directory shown is the current directory. With the -l argument, produce an unabbreviated printout; use of the ~ notation is suppressed. ksh, ksh93 The Korn shell built-in cd command can be in either of two forms. In the first form it changes the current directory to arg. If arg is - the directory is changed to the previous directory. The shell variable HOME is the default arg. The environment variable PWD is set to the current directory. If the PWD is changed, the OLDPWD environment variable shall also be changed to the value of the old working directory, that is, the current working directory immediately prior to the call to change directory (cd). The shell variable CDPATH defines the search path for the directory containing arg. Alternative directory names are separated by a colon (:). The default path is null (specifying the current directory). The current directory is specified by a null path name, which can appear immediately after the equal sign or between the colon delimiters anywhere else in the path list. If arg begins with a `/', `.', or `..', then the search path is not used. Otherwise, each directory in the path is searched for arg. If unsuccessful, cd attempts to change directories to the pathname formed by the concatena- tion of the value of PWD, a slash character, and arg. -L Handles the operation dot-dot (..) logically. Symbolic link components are not resolved before dot-dot components are processed. -P Handles the operand dot-dot physically. Symbolic link components are resolved before dot-dot components are processed. If both -L and -P options are specified, the last option to be invoked is used and the other is ignored. If neither -L nor -P is specified, the operand is handled dot-dot logically. The second form of cd substitutes the string new for the string old in the current directory name, PWD and tries to change to this new directory. The cd command cannot be executed by rksh. Because a new process is created to execute each command, cd would be ineffective if it were written as a normal command; therefore, it is recognized by and is internal to the Korn shell. (See pwd(1), sh(1), and chdir(2)). OPERANDS
The following operands are supported: directory An absolute or relative pathname of the directory that becomes the new working directory. The interpretation of a relative pathname by cd depends on the CDPATH environment variable. OUTPUT
If a non-empty directory name from CDPATH is used, an absolute pathname of the new working directory is written to the standard output as follows: "%s ", <new directory> Otherwise, there is no output. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of cd: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. CDPATH A colon-separated list of pathnames that refer to directories. If the directory operand does not begin with a slash ( / ) charac- ter, and the first component is not dot or dot-dot, cd searches for directory relative to each directory named in the CDPATH variable, in the order listed. The new working directory sets to the first matching directory found. An empty string in place of a directory pathname represents the current directory. If CDPATH is not set, it is treated as if it were an empty string. HOME The name of the home directory, used when no directory operand is specified. OLDPWD A pathname of the previous working directory, used by cd-. PWD A pathname of the current working directory, set by cd after it has changed to that directory. EXIT STATUS
The following exit values are returned by cd: 0 The directory was successfully changed. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: csh, ksh, sh +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), ksh(1), ksh93(1), pwd(1), sh(1), chdir(2), attributes(5), environ(5), standards(5) SunOS 5.11 8 Apr 2008 cd(1)
All times are GMT -4. The time now is 11:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy