understanding thread in perl Post: 302696023

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help understanding perl script error

I solicited this site earlier this week and got a good answer for a perl Script so I made this script from what understood from the answers But now I have a bug and I'm stump. It doesn't parse correctly the Output it stays on the first line My $f2 and reprints in a endless loop I'm sure there...

2. Shell Programming and Scripting

perl command understanding

Hi All, Can you please help me interpret the following command. Which I am not able to understand. Also can you please illustrate what it is used for. perl -pi -e 's/\015//g' text_file.dat Regards

3. Shell Programming and Scripting

Perl: Understanding @allwords

Hi guys, Here is the code: my @allwords = (); my %seen=(); foreach my $curr (@allwords) { $seen{$curr} = 1; } @allwords = keys %seen; my question is: what will @allwords now contain, or how would the entries in the @allwords array be different after this manipulation? Thank...

4. Shell Programming and Scripting

Understanding perl statement

can someone help me how to interpret this line? my ($class, $hashref) = @_; my $portfolio = {}; if ($hashref->{portfolio_id}) { ($portfolio) = GEmySQL->get ("select * from portfolio where portfolio.id=$hashref->{portfolio_id}"); } =============== Question: how do...

5. Shell Programming and Scripting

Help understanding Perl code.

Well, I found myself trying to fix some Perl code (Ive never done any Perl in my life) and I pinpointed the place where the bug could be. But to be sure I have to know what does a few line of code mean: $files_lim =~ (/^\d*$/) $files_lim =~ (/^\d*h$/)$files_age =~ s/h//The code where this was...

6. Shell Programming and Scripting

Help understanding some Perl code.

7. Programming

Understanding perl code

What is the difference between the two statements below? A: $a->{"$fruit"}->{"$color"}->{size} = $size B: $size = $a->{"$fruit"}->{"$color"}->{size} Please assist. Thanks!

8. Shell Programming and Scripting

Help with perl code understanding

Hi, I need to understand below perl code, can some one advise me. perl -MDate::Parse -e'BEGIN{$main::now=time;$main::old=(time-60*30)}' -nE'if(/^(\w+\s+\d+\s+\d+:\d+:\d+)/) {$t=str2time $1; $t > $old && $t < $now && print}'

9. Shell Programming and Scripting

Understanding an example of perl map() function

Hello, I have many folders under which there is always a file with the same name, which contains the data I need to process later. A perl oneliner was borrowed perl -e 'print "gene_id\t", join("\t", map {/(.*)\//; $1} @ARGV),"\n";' *_test.trim/level.csvto make a header so that each column...

10. Shell Programming and Scripting

Help understanding perl script

Hello, A former sys admin placed this script on one of our boxes and it needs to be adjusted, but I'm not familiar with perl. Can someone help break this down for me? I'm particularly interested in the -mtime function. What's the time frame being referenced here. ...

LEARN ABOUT HPUX

vxiod

vxiod(1M)																 vxiod(1M)

NAME

       vxiod - start, stop, and report on Veritas Volume Manager I/O threads

SYNOPSIS

       vxiod

       vxiod [-f ] [set count]

DESCRIPTION

       The  vxiod utility starts, stops, or reports on Veritas Volume Manager (VxVM) I/O kernel threads.  An I/O thread provides a process context
       for performing I/O in VxVM.

       When the vxio module is loaded, 16 I/O threads are created, plus 2 threads per additional CPU for a system with more than 8 CPUs, up  to  a
       maximum	of  64	threads.  At least one I/O thread must be running while the vxio module is loaded, and the number of I/O threads cannot be
       forced to zero.

       When invoked with no arguments, vxiod prints the current number of I/O threads to the standard output.

       The number of threads that is required for handling I/O requests depends on the system load and usage.  If volume recovery seems to proceed
       more slowly at times, it may be possible to improve its performance by increasing the number of I/O threads up to a maximum of 64.

KEYWORDS

       set	 When  invoked with the set keyword, vxiod creates the number of I/O threads specified by count.  If more volume I/O threads exist
		 than are specified by count, the excess processes terminate.  If more than the maximum number(64) are specified,  the  requested
		 number is silently truncated to that maximum.

OPTIONS

       -f	 This option has no effect from release 5.0 onward.  The number of I/O threads cannot be reduced to zero.

EXIT CODES

       The  vxiod  utility  prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O request occurs within a I/O
       thread, the state of that I/O request is not reflected in the exit status for vxiod.  Otherwise, vxiod returns a non-zero  exit	status	on
       error.

       Usage  errors  result in an exit status of 1 and a usage message.  If the requested number of threads cannot be created, the exit status is
       2, and the number of threads that were successfully started is reported.  If any other error occurs, the exit status is 3.

FILES

       /dev/vx/iod		     The device used to report on and start volume I/O threads.

NOTES

       Veritas Volume Manager I/O threads cannot be killed directly through the use of signals.

       Depending on the operating system, VxVM I/O threads may not appear in the list of processes that is output by the ps command.   The  number
       of I/O threads that is currently running can be determined by running vxiod.

SEE ALSO

       fork(2), ps(1), vxconfigd(1M), vxdctl(1M), vxintro(1M), vxio(7), vxiod(7)

VxVM 5.0.31.1							    24 Mar 2008 							 vxiod(1M)