Sponsored Content
Top Forums Shell Programming and Scripting How do display a warning message? Post 302407221 by dunkar70 on Wednesday 24th of March 2010 09:40:06 PM
Old 03-24-2010
First, UNIX is case sensitive so the command is cd, not CD. You can type "man cd" to get the manual page for the command. Second, the decision to include a slash in your path is important. Starting a path with it denotes the root as the starting point and it denotes a full path. Ending the path with it denotes a directory, which is assumed when using the cd command. Trying to use the cd command with a file generate an error.

In short, cd can use relative paths or full paths.

Starting from the directory you listed:
Code:
/home/me/blah

you can type either of two commands to get to the "me" directory:
- Full path is always available regardless of the current working directory:
Code:
cd /home/me

- Relative path is only available if the current directory is the immediate child of the /home/me directory:
Code:
cd ../me

Both forms of the command have advantages and disadvantages. The decision to use one over the other depends on 1) if you know the full path, 2) if the script must be portable within a set of files and directories, and 3) if it makes sense.

Error/warning messages will automatically be displayed if you 1) try to cd into a file or 2) into a directory that does not exist.

Last edited by dunkar70; 03-24-2010 at 10:42 PM.. Reason: Adding clarity
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to display message when starting a terminal

Hello all, I would like a message to be displayed on the shell when someone opens up the terminal - something like a welcome msg with date and time. I know how to do this by running the shell commands but dont know how to display it when a user opens up the terminal? Thanks in advance (27 Replies)
Discussion started by: mrudula009
27 Replies

2. UNIX Desktop Questions & Answers

Script that will display a short message

Can anyone point me to the right direction on how to write a simple script that will display a message on any terminal when implemented? Basically I need it so the script runs at a certain time, say April 30, 2010 and that the message will be displayed to me no matter which terminal I am logged... (2 Replies)
Discussion started by: jmack123
2 Replies

3. UNIX for Dummies Questions & Answers

Display message on screen and flat file at same time

Hi guys, I have a script that call another, the other displays de message and I can print directly to the flat file, but in one command I am searchig that this message can be displayed in the screen and in the flat file in one command. I am doing something like this: var=$(./Example.sh)... (2 Replies)
Discussion started by: pipoca
2 Replies

4. Shell Programming and Scripting

How to grep for message and if found display filename?

Hi i'm new to the forum and was hoping someone could help me with the following query. I do alot of testing and have hundreds of log files output. I have a script (someone else wrote) which finds all the passed and failed logs and puts a number in a column onto a webpage: e.g: Pass ... (4 Replies)
Discussion started by: defamer
4 Replies

5. Shell Programming and Scripting

Display a message if the server is prompting

Hello i have to perform a sftp from server "A" to server "B"(remote server). when i execute the sftp command it prompts for password. right now we haven't establish the ssh key exchange so we have to dispaly a error message if it prompts for password. how can i perform it please help (0 Replies)
Discussion started by: urfrnddpk
0 Replies

6. Shell Programming and Scripting

How to display a message if program hangs(takes too long)

I have a ksh script (script1) that calls another ksh script (script2). If script2.ksh hangs or takes too long to execute I want script1.ksh to kill the call to script2.ksh and instead just display "Script2 can't run right now". Could someone help me with coding this? (1 Reply)
Discussion started by: mrskittles99
1 Replies

7. Shell Programming and Scripting

Refrain the Message of File Not exists display out

Hi All, Would like to ask on how to refrain the message file not exists from display out. if ; then When it execute, the OS will throw the error file does not exists ls: 0653-341 The file COL_*/*.CTL does not exist. Thanks. (3 Replies)
Discussion started by: ckwan
3 Replies

8. Solaris

Display Message Question

I'm have a script that I am creating and I want the dmesg command to only show output for the current day and the day before. What would be the command to make this work? Thanks (8 Replies)
Discussion started by: MattyJ2009
8 Replies

9. Shell Programming and Scripting

Search for a tag and display a message if not found.

Hi All, I am working with a XML file. Below is part for the file. <Emp:Profile> <Emp:Description>Admin</Emp:Description> <Emp:Id>12347</Emp:Id> </Emp:Profile> <Emp:Profile> ... (7 Replies)
Discussion started by: Girish19
7 Replies

10. Shell Programming and Scripting

Bash function to suppress warning message for specific text and display prompt

In the below bash function multiple variants are input and stored in a variable $variant, and each is written to an out file at c:/Users/cmccabe/Desktop/Python27/out.txt stored on a separate line. # enter variant phox2b() { printf "\n\n" printf "What is the id of the patient getting... (0 Replies)
Discussion started by: cmccabe
0 Replies
filename(n)						       Tcl Built-In Commands						       filename(n)

__________________________________________________________________________________________________________________________________________________

NAME
filename - File name conventions supported by Tcl commands _________________________________________________________________ INTRODUCTION
All Tcl commands and C procedures that take file names as arguments expect the file names to be in one of three forms, depending on the current platform. On each platform, Tcl supports file names in the standard forms(s) for that platform. In addition, on all platforms, Tcl supports a Unix-like syntax intended to provide a convenient way of constructing simple file names. However, scripts that are intended to be portable should not assume a particular form for file names. Instead, portable scripts must use the file split and file join com- mands to manipulate file names (see the file manual entry for more details). PATH TYPES
File names are grouped into three general types based on the starting point for the path used to specify the file: absolute, relative, and volume-relative. Absolute names are completely qualified, giving a path to the file relative to a particular volume and the root directory on that volume. Relative names are unqualified, giving a path to the file relative to the current working directory. Volume-relative names are partially qualified, either giving the path relative to the root directory on the current volume, or relative to the current directory of the specified volume. The file pathtype command can be used to determine the type of a given path. PATH SYNTAX
The rules for native names depend on the value reported in the Tcl array element tcl_platform(platform): mac On Apple Macintosh systems, Tcl supports two forms of path names. The normal Mac style names use colons as path separators. Paths may be relative or absolute, and file names may contain any character other than colon. A leading colon causes the rest of the path to be interpreted relative to the current directory. If a path contains a colon that is not at the beginning, then the path is interpreted as an absolute path. Sequences of two or more colons anywhere in the path are used to construct relative paths where :: refers to the parent of the current directory, ::: refers to the parent of the parent, and so forth. In addition to Macintosh style names, Tcl also supports a subset of Unix-like names. If a path contains no colons, then it is interpreted like a Unix path. Slash is used as the path separator. The file name . refers to the current directory, and .. refers to the parent of the current directory. However, some names like / or /.. have no mapping, and are interpreted as Macin- tosh names. In general, commands that generate file names will return Macintosh style names, but commands that accept file names will take both Macintosh and Unix-style names. The following examples illustrate various forms of path names: : Relative path to the current folder. MyFile Relative path to a file named MyFile in the current folder. MyDisk:MyFile Absolute path to a file named MyFile on the device named MyDisk. :MyDir:MyFile Relative path to a file name MyFile in a folder named MyDir in the current folder. ::MyFile Relative path to a file named MyFile in the folder above the current folder. :::MyFile Relative path to a file named MyFile in the folder two levels above the current folder. /MyDisk/MyFile Absolute path to a file named MyFile on the device named MyDisk. ../MyFile Relative path to a file named MyFile in the folder above the current folder. unix On Unix platforms, Tcl uses path names where the components are separated by slashes. Path names may be relative or absolute, and file names may contain any character other than slash. The file names . and .. are special and refer to the current direc- tory and the parent of the current directory respectively. Multiple adjacent slash characters are interpreted as a single sepa- rator. The following examples illustrate various forms of path names: / Absolute path to the root directory. /etc/passwd Absolute path to the file named passwd in the directory etc in the root directory. . Relative path to the current directory. foo Relative path to the file foo in the current directory. foo/bar Relative path to the file bar in the directory foo in the current directory. ../foo Relative path to the file foo in the directory above the current directory. windows On Microsoft Windows platforms, Tcl supports both drive-relative and UNC style names. Both / and may be used as directory sep- arators in either type of name. Drive-relative names consist of an optional drive specifier followed by an absolute or relative path. UNC paths follow the general form \servernamesharenamepathfile, but must at the very least contain the server and share components, i.e. \servernamesharename. In both forms, the file names . and .. are special and refer to the current directory and the parent of the current directory respectively. The following examples illustrate various forms of path names: \Hostshare/file Absolute UNC path to a file called file in the root directory of the export point share on the host Host. Note that repeated use of file dirname on this path will give //Host/share, and will never give just /fB//Host/fR. c:foo Volume-relative path to a file foo in the current directory on drive c. c:/foo Absolute path to a file foo in the root directory of drive c. fooar Relative path to a file bar in the foo directory in the current directory on the current volume. foo Volume-relative path to a file foo in the root directory of the current volume. \foo Volume-relative path to a file foo in the root directory of the current volume. This is not a valid UNC path, so the assumption is that the extra backslashes are superfluous. TILDE SUBSTITUTION
In addition to the file name rules described above, Tcl also supports csh-style tilde substitution. If a file name starts with a tilde, then the file name will be interpreted as if the first element is replaced with the location of the home directory for the given user. If the tilde is followed immediately by a separator, then the $HOME environment variable is substituted. Otherwise the characters between the tilde and the next separator are taken as a user name, which is used to retrieve the user's home directory for substitution. The Macintosh and Windows platforms do not support tilde substitution when a user name follows the tilde. On these platforms, attempts to use a tilde followed by a user name will generate an error that the user does not exist when Tcl attempts to interpret that part of the path or otherwise access the file. The behaviour of these paths when not trying to interpret them is the same as on Unix. File names that have a tilde without a user name will be correctly substituted using the $HOME environment variable, just like for Unix. PORTABILITY ISSUES
Not all file systems are case sensitive, so scripts should avoid code that depends on the case of characters in a file name. In addition, the character sets allowed on different devices may differ, so scripts should choose file names that do not contain special characters like: <>:"/|. The safest approach is to use names consisting of alphanumeric characters only. Also Windows 3.1 only supports file names with a root of no more than 8 characters and an extension of no more than 3 characters. On Windows platforms there are file and path length restrictions. Complete paths or filenames longer than about 260 characters will lead to errors in most file operations. KEYWORDS
current directory, absolute file name, relative file name, volume-relative file name, portability SEE ALSO
file(n), glob(n) Tcl 7.5 filename(n)
All times are GMT -4. The time now is 12:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy