07-31-2012
The $ sign expands (=replaces) parameters/variables to (with) their contents. 1, 2, ... are positional parameters, of which $# is the count; $? yields the exit code/status of your last command. Read the man page of your shell.
10 More Discussions You Might Find Interesting
1. Solaris
My company has a product that is running on JBoss on Solaris against Oracle 8.1.7. We are having an issue with the server process and high CPU utilization. During this time, and only during this time, we are experiencing database locks that will not let go. A 'ps -L' on the server process... (5 Replies)
Discussion started by: hosierdm
5 Replies
2. UNIX for Dummies Questions & Answers
I've got a really weird situation here.... the same IP address keeps popping up in porn spam that I have rec'd in 2 different email accts. It looks to me like it's coming from UC Davis, and I suspect someone there, so I am hoping you all can verify the same thing before I call the person on this... (0 Replies)
Discussion started by: christinef
0 Replies
3. Cybersecurity
Hi,
I am stuck with a tricky situation in which one of my applications is flooding the network with UDP messages. The architecture of the application is not supposed to do so. Neither is there any place where the application will go into an infinite loop sending UDP messages over the network. To... (3 Replies)
Discussion started by: diganta
3 Replies
4. HP-UX
hi,
if I do top, I get
Memory: 19277012K (5868296K) real, 33860312K (11294208K) virtual, 795392K free
If I do swapinfo -tm I get:
% swapinfo -tm
Mb Mb Mb PCT
TYPE AVAIL USED FREE USED
dev 16384 0 16383 0%
dev ... (3 Replies)
Discussion started by: JamesByars
3 Replies
5. Shell Programming and Scripting
I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config.
I am not sure if I can do this with BASH scripting.
I have set up password less login by adding my public key to authorized_keys file, it works.
I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
6. Shell Programming and Scripting
Hi Guys,
I am running solaris and I need help in deciphering the following commands:
dir_t1=`echo $0|nawk -F'/' '{print NF}'`
dir_t2=`expr $dir_t1- 1`
dir_t3=`echo $0|cut -d'/' -f1-$dir_t2`
export dir_t2
What will be the value for dir_t3?
Please help !!!!!!!!!!!!!!! (5 Replies)
Discussion started by: Phuti
5 Replies
7. Shell Programming and Scripting
Guys,
I am going through an existing code in production and found the following lines. I have used "sed" before but am unable to decipher the following statement. :(
echo ${F_NAME} | sed 's/\(.*\)............/\1/'
Any help is greatly appreciated.
Cheers,
Sid (6 Replies)
Discussion started by: sid1982
6 Replies
8. UNIX for Advanced & Expert Users
Two question here, but it's only one on the protocol point of view.
If two persons use the same key to connect to a SSH server is there a risk they can decipher the other tunnel. In other terms is that less safe than if they have two separate keys.
Same question if two persons use the same user... (2 Replies)
Discussion started by: moi
2 Replies
9. Shell Programming and Scripting
ssh-add -t 30 >/dev/null 2>&1
LOGNAME=`whoami`
cp $HOME/.ssh/known_hosts $HOME/.ssh/known_hosts.org grep -v localhost
$HOME/.ssh/known_hosts.org > $HOME/.ssh/known_hosts
ssh -1 -f -l $LOGNAME -o "ForwardX11 yes" -o "StrictHostKeyChecking no"
-L 6003:1.1.1.1:2222 ext-proxy-2 sleep 5... (1 Reply)
Discussion started by: llcooljatt
1 Replies
10. SuSE
ssh-add -t 30 >/dev/null 2>&1
LOGNAME=`whoami`
cp $HOME/.ssh/known_hosts $HOME/.ssh/known_hosts.org
grep -v localhost $HOME/.ssh/known_hosts.org > $HOME/.ssh/known_hosts
ssh -1 -f -l $LOGNAME -o "ForwardX11 yes" -o "StrictHostKeyChecking no" -L 6003:195.244.210.107:2222 ext-proxy-2 sleep 5... (7 Replies)
Discussion started by: llcooljatt
7 Replies
LEARN ABOUT SUSE
platform::shell
platform::shell(n) Tcl Bundled Packages platform::shell(n)
__________________________________________________________________________________________________________________________________________________
NAME
platform::shell - System identification support code and utilities
SYNOPSIS
package require platform::shell ?1.1.4?
platform::shell::generic shell
platform::shell::identify shell
platform::shell::platform shell
_________________________________________________________________
DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.
This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
requirement is that the other shell (identified by its path), is actually executable on the current machine.
While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell
this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.
For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed
packages, versus the architecture of the shell running the repository software.
COMMANDS
platform::shell::identify shell
This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.
platform::shell::generic shell
This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.
platform::shell::platform shell
This command returns the contents of tcl_platform(platform) for the specified Tcl shell.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform::shell 1.1.4 platform::shell(n)