01-27-2017
Quote:
Originally Posted by
Peasant
If i'm not mistaken backquotes are still the lowest common denominator for command substitution if you wish your scripts to work anywhere without touching
This is an interesting argument.
IMHO the "gold standard" of portability is POSIX: if something is POSIX, then it can (and should) be used, if it not, it should be handled with extreme care (and eventually not be used in absence of compelling reasons why it should).
The construct
$(..) now
is in fact the POSIX-standard for doing this (subshells) and backticks
`...` are deprecated. This is why i use the former rather than the latter and recommend this practice to others.
For the same reason i write i.e.
tail -n 5 instead of
tail -5. The former is POSIX, the latter deprecated. It may be that there is some (really old) system out there which would not recognise the new syntax but only the old one. This risk i am willing to take because, on the the other hand, there might be a really new system which has cut off old behaviorisms and only understands the current syntax.
I hope this helps.
bakunin
Moderator's Comments:
|
|
PS: this discussion is very interesting but we are getting off topic in relation the threads original theme. If anyone wants to continue this i suggest to split this thread and carry on in a new one. Just post here if you want to contribute and i will take care of the splitting if there are any takers.
|
|
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Can someone explain the difference between backticks and system when
evaluated in these if statements:
sub getDate {
print "start date\n";
if ( system("/bin/date") ) {
print "can't get date\n";
exit(2);
}
print "finish date\n";
}
Returns the following:
start date
Thu... (5 Replies)
Discussion started by: gjkeenan
5 Replies
2. Shell Programming and Scripting
Hi, I'm trying to do something like this: range= `expr `date '+%m'` - 1` and it does not work. How can I tell it to evaluate an expression within another expression evaluation? I was at first worried that `date '+%m'` would return a string but apparently expr does the math okay normally, so the... (3 Replies)
Discussion started by: jeriryan87
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I would like to change some lines in my mysql-dump, because there a syntax problems with some version of mysql.
I 'd like to change
USE ´someDatabase´;
to
USE someDatabase;
(without backticks) using the sed command in the shell
Thanks & best regards
Bernd (5 Replies)
Discussion started by: bjb
5 Replies
4. Shell Programming and Scripting
I'm always concerned I might be abusing backticks within my scripts. A current script I'm writing has this for example:
stripscriptname=`echo $scriptname | sed 's/\(.*\)\..*/\1/'`
stripsearch=`echo $searchpattern | tr -d ' ,/'`
Both of these variables are set inside the script (in fact,... (2 Replies)
Discussion started by: mglenney
2 Replies
5. Shell Programming and Scripting
Hey all. Just a fast question, what is the technical difference between using back ticks and using xargs to perform a command?
Here's an example
Find /mydir -name *.conf |xargs rm
Vs
Rm 'find /mydir -name *.conf'
Is there a performance hit? I know they do the same thing but which is... (1 Reply)
Discussion started by: msarro
1 Replies
6. Red Hat
Hi everyone. This is a bit of a perl/linux mixed question. I am trying to redirect STDOUT of chsh by using the following line of perl code.
system ("chsh -s /sbin/nologin $testing 1>/dev/null");
This should redirect STDOUT to /dev/null but it won't do that for some odd reason. Any ideas or... (6 Replies)
Discussion started by: austinharris43
6 Replies
7. Shell Programming and Scripting
Input file:
'data_1'
'data_10'
'data1311'
'235data_13'
Desired output:
data_1
data_10
data1311
235data_13
Can I know how to remove back tick"'" in a file?
Many thanks for advice. (3 Replies)
Discussion started by: perl_beginner
3 Replies
8. Shell Programming and Scripting
I have been testing a new script and cannot figure out why my `cat spath` will not execute on the remote machine?
sudo ssh -p 22344 -o "PasswordAuthentication no" -o "HostbasedAuthentication yes" -l testuser 192.168.1.6 "find `cat spath` -depth"
cat: spath: No such file or directory
but... (0 Replies)
Discussion started by: metallica1973
0 Replies
9. Shell Programming and Scripting
I'm trying to make a dialog window that prints the output of grep that takes the output of find. Unfortunately my nested backticks don't work.
Here is the dialog window:
dialog --stdout --title "test" --backtitle "test" --msgbox "Test:\n `grep -l "${tablica}" `find $string``" 16 60I think I... (2 Replies)
Discussion started by: Starting_Leaf
2 Replies
LEARN ABOUT HPUX
aio_proc_threads
aio_proc_threads(5) File Formats Manual aio_proc_threads(5)
NAME
aio_proc_threads - maximum number of process threads allowed in AIO pool
VALUES
Failsafe
Default
Allowed values
Recommended values
DESCRIPTION
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous
I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools)
created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilization of CPU
time vs. I/O resources, four dynamic tunables are available to customize the behavior of this thread pool: aio_proc_threads(5),
aio_proc_thread_pct(5), aio_req_per_thread(5), and aio_monitor_run_sec(5). Please see individual manpages for details on each of these
tunables.
The tunable specifies, on a per-process basis, the maximum number of process threads that can be used by the POSIX AIO system as kernel
threads for issuing I/Os.
This tunable interacts with in the following way: the maximum number of threads used for AIO will be the smaller of the two values defined
by the two tunables, i.e.:
This allows the number of AIO threads to vary dynamically with but to always be bound by an absolute limit of
Who Is Expected to Change This Tunable?
System administrators that run applications requiring heavy usage of POSIX AIO to filesystems.
Restrictions on Changing
This tunable is dynamic. Changes to to this tunable take effect immediately for new processes started after the change. They also impact
existing processes, but the speed with which the changes propagate to running processes is determined by the tunable
When Should the Value of This Tunable Be Raised?
should be raised for applications that do not use very many threads for their own work, but desire high performance from the POSIX AIO sub-
system.
What Are the Side Effects of Raising the Value of This Tunable?
Some applications that use POSIX AIO but also require a large number of threads may find that they are unable to create new threads. (This
could happen if the POSIX AIO thread pool ends up using too many of a process' allowable threads.)
In addition, using a larger number of kernel threads might lead to increased CPU utilization.
When Should the Value of This Tunable Be Lowered?
should be lowered when POSIX AIO performance is acceptable but applications using POSIX AIO are seeing errors when trying to create new
threads for other work.
What Are the Side Effects of Lowering the Value of This Tunable?
By ultimately reducing the number of threads available to handle POSIX AIO requests, overall I/O throughput of the POSIX AIO subsystem
could be reduced.
What Other Tunables Should Be Changed at the Same Time as This One?
interacts with this tunable by setting a limit on the number of AIO threads based on a percentage of the maximum number of allowable
process threads. This allows the AIO thread pools to respond dynamically to changes in
defines the desired relationship between the number of POSIX AIO kernel threads and the number of I/Os to be serviced.
defines how often (in seconds) the AIO thread mechanism will monitor itself for adherence to the constraints defined by the tunables above.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), aio_proc_thread_pct(5), aio_req_per_thread(5), aio_monitor_run_sec(5).
Tunable Kernel Parameters aio_proc_threads(5)