Use parameter expansion over a parameter expansion in bash.
Hello All,
Could you please do help me here as I would like to perform parameter expansion in shell over a parameter expansion.
Let's say I have following variable.
Now to get only nat I could do following.
Here in this approach I am creating a temporary variable path1 and again performing parameter expansion, how about if I want to perform this in single time without having temporary variable? I have tried it like:
Which is giving me an error. Any help, guidance is appreciated.
Thanks,
R. Singh
This User Gave Thanks to RavinderSingh13 For This Post:
Hi all-
I have a variable that contains a web page:
echo $STUFF
<html> <head> <title>my page</title></head> <body> blah blah etc..
Can I use the shell's parameter expansion abilities to remove just the tags?
I thought that FIXHTML=${STUFF//<*>/} might do it, but it didn't seem to... (2 Replies)
Hi ,
could anyone help me out with this problem.
sample.txt has this content :
u001- this is used for project1 ||
u002- this is used for p2|| not to be printed
u003- this is used
for project3 ||
u004- this is
used for p4 ||
u005- this is used for project5 ||
u006- this is used for p6... (9 Replies)
Say you have this numeric variable that can be set by the user but you never want it to leave a certain range when it gets printed. How could you use parameter expansion such that it will never expand outside of that boundary? Thanks
---------- Post updated at 11:09 PM ---------- Previous update... (3 Replies)
Hi -
I am trying to do a simple config file with known variable names in it, e.g.:
contents of config file a.conf: -a
-b $work
-c $host
simplified contents of bash script file: work='trunk'
host='alaska'
opts=$(tr '\n' ' ' < a.conf)
opts="$opts $*"
mycommand $opts arg1 arg2
The... (3 Replies)
I'm trying to write a script that parses my music collection and hard link some filenames that my media player doesn't like to other names.
To do this I need to extract the name and remove alla non ASCII characters from that and do a cp -l with the result.
Problem is this:
22:16:58 $... (8 Replies)
Hello experts,
I am exploring parameter expansion, and trying to cut the fields in a URL.
Following is the requirement:
I have
// abc.nnt /dir1/dir2/dir3/dir4/somefile.java
What i need to get is the path after dir3, and dir3 will be passed.
output that i need is... (1 Reply)
I have made the following examples that print various parameter expansions
text: iv-hhz-sac/hpac/hhz.d/iv.hpac..hhz.d.2016.250.070018.sac
(text%.*): iv-hhz-sac/hpac/hhz.d/iv.hpac..hhz.d.2016.250.070018
(text%%.*): iv-hhz-sac/hpac/hhz
(text#*.): d/iv.hpac..hhz.d.2016.250.070018.sac... (2 Replies)
#!/bin/bash
SNMPW='/usr/bin/snmpwalk'
while read h i
do
loc=$($SNMPW -v3 -u 'Myusername' -l authPriv -a SHA -A 'Password1' -x AES -X 'Password2' $i sysLocation.0 2>/dev/null)
loc=${loc:-" is not snmpable."}
loc=${loc##*: }
loc=${loc//,/}
echo "$i,$h,$loc"
done < $1
My question is ... ... (1 Reply)
I am trying to become more fluent with the interworking of bash and minimize the number of external calls.
Sample Data. This will be the response of the snmp query.
SNMPv2-MIB::sysName.0 = STRING: SomeHostName
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1745... (5 Replies)
Example data
$ ls *somehost*
10.10.10.10_somehost1.xyz.com.log
11.11.11.11_somehost2.xyz.com.log
#!/bin/bash
#FILES="*.log"
FILES=${FILES:-*.log}
for x in $FILES
do
ip="${x%%_*}" # isolate IP address
x="${x##*_}" # isolate hostname
hnam="${x%.*}" # Remove the ".log"... (2 Replies)
Discussion started by: popeye
2 Replies
LEARN ABOUT OSF1
link
link(2) System Calls Manual link(2)NAME
link - Creates a hard link to an existing file on the local file system
SYNOPSIS
#include <unistd.h>
int link ( const char *path1, const char *path2 );
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link(): XSH5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
PARAMETERS
Points to the pathname of an existing file. Points to the pathname for the directory entry to be created. If the path2 parameter names a
symbolic link, an error is returned.
DESCRIPTION
The link() function creates an additional hard link (directory entry) for an existing file. The old and the new link share equal access
rights to the underlying object. The link() function atomically creates a new link for the existing file and increments the link count of
the file by one.
Both the path1 and path2 parameters must reside on the same file system. A hard link to a directory cannot be created.
Upon successful completion, the link() function marks the st_ctime field of the file for update, and marks the st_ctime and st_mtime fields
of the directory containing the new entry for update.
A process must have write permission in the target directory with respect to all access control policies configured on the system.
See symlink(2) for information about making symbolic links, including Context Dependent Symbolic Links (CDSLs).
RETURN VALUES
Upon successful completion, the link() function returns a value of 0 (zero). If the link() function fails, a value of -1 is returned, no
link is created, and errno is set to indicate the error.
ERRORS
If the link() function fails, errno may be set to one of the following values: The requested link requires writing in a directory with a
mode that denies write permission, or a component of either the path1 or path2 parameter denies search permission. The requested link
requires writing in a directory to which the process does not have write access with respect to one or more of the system's configured
access policies. The directory in which the entry for the new link is being placed cannot be extended because the user's quota of disk
blocks on the file system containing the directory has been exhausted. The link named by the path2 parameter already exists. The path1 or
path2 parameter is an invalid address. [Tru64 UNIX] An I/O error occurred when updating the directory. Too many links were encountered in
translating path1 or path2. The number of links to the file named by path1 would exceed LINK_MAX. The length of the path1 or path2 string
exceeds PATH_MAX or a pathname component is longer than NAME_MAX. The file named by the path1 parameter does not exist or the path1 or
path2 parameter is an empty string. The directory in which the entry for the new link is being placed cannot be extended because there is
no space left on the file system containing the directory. A component of either path prefix is not a directory. The file named by the
path1 parameter is a directory. The requested link requires writing in a directory on a read-only file system. The link named by the
path2 parameter and the file named by the path1 parameter are on different file systems.
[Tru64 UNIX] For NFS file access, if the link() function fails, errno may also be set to one of the following values: Indicates that the
system file table is full or there are too many files currently open in the system. Indicates a stale NFS file handle. An opened file was
deleted by the server or another client; a client cannot open a file because the server has unmounted or unexported the remote directory;
or the directory that contains an opened file was unmounted or unexported by the server.
RELATED INFORMATION
Commands: link(1), unlink(1)
Functions: unlink(2), symlink(2)
Standards: standards(5) delim off
link(2)