In this special case there is no effective difference between "$*" and "$@", because in bash the cd builtin accepts only one argument, the name of the directory you want to change to.
In ksh, cd takes optionally a second argument.
where old ist substituted with new in the current directory name and then changed to this directory, like
In this special case it would make a difference, because "$@" would keep two arguments intact, even if they contain whitespace, whereas "$*" would combine arg1 and arg2 into one string.
Hi guys,
I have no idea on unix but suddenly, my cobol programs calls a unix script that i know nothing about.
can you guys interpret these lines for me?
i know its a print command but I want to actually know how many copies it prints.
qprt -da -P $1 -t '6' -i '6' -l '70' $2
qprt -da... (1 Reply)
Could you interpret the following sed and awk command for me?
command:
cat tempfile2 |sed "s/\(BUILD-3-.*-\.-\)\(.*\..*\..*\)/\2/" | awk '{printf "%-8.8s %-23.23s %-30.30s %-50.50s\n", $1,$2,$3,substr($0,index($0,$4))}' > outfile2 2>/dev/null
input:(data in tempfile2)... (1 Reply)
Hi,
So I am new to Unix, and I need to check the performance of some apps I am running. But I don't know how to interpret the output from TOP.
Could somebody please explain the difference between the different values. And also explain how I can have a process which has a %CPU > 100?
... (7 Replies)
hi
I have a text file abc.txt as below
a = 0
b = 1
c = 3
i want to interpret this file i.e. if number corresponding to 'a' is 0 i want to run a script script.bash .
How do do that? (4 Replies)
I have collected data of Number of L2 cache misses using PAPI. I had run an MPI application with 4 threads (mpirun -np 4) and each thread reads the cache misses in L2. Each thread outputs data for every timestamp. eg:
Timestamp data
xxx530 thread# 0 2136
xxx531 thread# 0 ... (0 Replies)
I know $0 is the entire file's contents (at least I think that is what it is!), but what exactly is: $0!~
This was a snippet from a larger line
awk '$0!~/^$/ {print $0}'
This deletes blank lines, but I want to know specifically the $0!~ part... I am guessing /^$/ is regex for blank line...... (5 Replies)
Can anyone tell me how to interpret this:
listpage="ls |more" (the spaces are there in the example)
$listpage
It's from my bash book and I'm not sure what it means (3 Replies)
hi All,
i have never used sed in Unix environment, but i have one script which is using this following command:
cat audit_session_rpt_MSP_20140331.lst|sed -n '/Apr 14/!p'| sed -n '/Page/!p'| sed -n '/UserName/!p' |\
egrep -v '^-|^=|^\*'|sed '/^$/d'|sed -e '1,7d'... (1 Reply)
I booted into single user mode with
/usr/sbin/reboot -- -s
but after doing a control -d
my
who -r
shows
run-level 3 Nov 17 14:07 3 0 S
I was expecting it to show run-level S
why is this still in run level 3?
thanks (1 Reply)
Discussion started by: goya
1 Replies
LEARN ABOUT OSX
pwd
PWD(1) BSD General Commands Manual PWD(1)NAME
pwd -- return working directory name
SYNOPSIS
pwd [-L | -P]
DESCRIPTION
The pwd utility writes the absolute pathname of the current working directory to the standard output.
Some shells may provide a builtin pwd command which is similar or identical to this utility. Consult the builtin(1) manual page.
The options are as follows:
-L Display the logical current working directory.
-P Display the physical current working directory (all symbolic links resolved).
If no options are specified, the -L option is assumed.
ENVIRONMENT
Environment variables used by pwd:
PWD Logical current working directory.
EXIT STATUS
The pwd utility exits 0 on success, and >0 if an error occurs.
SEE ALSO builtin(1), cd(1), csh(1), sh(1), getcwd(3)STANDARDS
The pwd utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BUGS
In csh(1) the command dirs is always faster because it is built into that shell. However, it can give a different answer in the rare case
that the current directory or a containing directory was moved after the shell descended into it.
The -L option does not work unless the PWD environment variable is exported by the shell.
BSD April 12, 2003 BSD