The output of this echo shows the 3 names in a single line which is perfectly fine.
But my doubt is with the below:
The output of this shows the 3 names in 3 lines.
Please see, now also I expected the same output because the variable a is already defined. When above I defined the variable "a", the command cat emp.lst was not quoted and hence variable "a" should not have accepted a newline character.
But this output says that the var. "a" has accepted the newline character.
How come this happen?
I'm having some peculiar performance issues with my Gigabit Lan.
I have some 100Mb devices so I can't do the necessary "jumbo Frame" tweaks for absolute optimum performance as I'd prevent them access.
I'm getting appauling transfer rates sending files to the linux machine, around 10 Mbps 3%... (0 Replies)
Whenever I sftped a particular gzipped file to a particular directory and then try to unzip it, I get Permission Denied error.
With this file even I cannot do chmod. though the file permissions are -rw-r--r--
When same file I sftp to a different location I am able to gunzip it.
Directory... (0 Replies)
Hi all,
Ok os heres my situation. I have created a database style program that stores a persons info (name,address,phone number etc.) in a file ("database"). after i read in all the values above, i assign them to a line variable:
line="$name^$address^$phonenum" >> phonebuk
as you can see... (1 Reply)
Hi!
I am working in korn shell. I want to reset the dimiliter for the set command to "|" but instead of a command prompt return I am getting something as below
After issuing the command I am getting this....as if the shell is expecting something else. Can anybody suggest what's the problem.
... (2 Replies)
Scenario:
Step 1. I'm logging into AIX server using user id called user1
Step 2. I'm traversing to home directory of user2
Note: This user2's home directory has the permissions drwxr-s---
Step 3. I'm issuing command pwd there. I'm getting the expected output.
Step 4. I'm issuing the... (3 Replies)
hi I keep getting an error with this nested if statement and am getting the error unexpected end of file, can anyone help me as to why this wont execute?
#!/bin/bash
#script to check wether the -i -v statements run correctly
removeFile ()
{
mv $1 $HOME/deleted
}... (3 Replies)
I am using bash and resetting IFS as below when reading the command line arguments. I do this so I can call my script as in Ex1.
Ex1: ./synt2d-ray3dmod.bash --xsrc=12/20/30
This allows me to split both sides so that when I do "shift"
I can get 12/20/30
What I do not understand is... (21 Replies)
Hi ,
i am in my initial learning phase of unix. i was going thru the function part.
below is the example which was there but i am not able to understand logic and the use of IFS(internal field separator)
lspath() {
OLDIFS="$IFS"
IFS=:
for DIR in $PATH ; do echo $DIR ; done
IFS="$OLDIFS"... (8 Replies)
Discussion started by: scriptor
8 Replies
LEARN ABOUT MOJAVE
echo
ECHO(1) BSD General Commands Manual ECHO(1)NAME
echo -- write arguments to the standard output
SYNOPSIS
echo [-n] [string ...]
DESCRIPTION
The echo utility writes any specified operands, separated by single blank (' ') characters and followed by a newline ('
') character, to the
standard output.
The following option is available:
-n Do not print the trailing newline character. This may also be achieved by appending 'c' to the end of the string, as is done by iBCS2
compatible systems. Note that this option as well as the effect of 'c' are implementation-defined in IEEE Std 1003.1-2001
(``POSIX.1'') as amended by Cor. 1-2002. Applications aiming for maximum portability are strongly encouraged to use printf(1) to sup-
press the newline character.
Some shells may provide a builtin echo command which is similar or identical to this utility. Most notably, the builtin echo in sh(1) does
not accept the -n option. Consult the builtin(1) manual page.
EXIT STATUS
The echo utility exits 0 on success, and >0 if an error occurs.
SEE ALSO builtin(1), csh(1), printf(1), sh(1)STANDARDS
The echo utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
BSD April 12, 2003 BSD