11-22-2006
Thanks for quick feedback!
For the time being I've decided to process the jobs sequentially i.o. parallel. By creating an array I can store the PID's to this array and use it for the waiting step.
8 More Discussions You Might Find Interesting
1. Linux
Dear linuxers,
I have a usb mess storage device.
My OS is rh as3 update2.
Each time I use the command
mount -t vfat /dev/sda1 /mnt/usb
I got the error "the device is not a valid block device".
I found from google that I should install the module sd_mod
I use the command
insmod sd_mod... (2 Replies)
Discussion started by: niukun
2 Replies
2. UNIX for Advanced & Expert Users
Hi all,
Please look into the following code :
int main()
{
char command;
int pid, ppid;
ppid = getpid(); /* Get the parent pid */
pid = fork(); /* Fork */
if ( pid ==0 )
{
sprintf( command, " gdb a.out %d ", ppid );
printf( "Command line is %s\n", command );
system( command... (3 Replies)
Discussion started by: asvija
3 Replies
3. Solaris
Dear Expert ,
We have L7 , when we power on we see on lcd messages "drive Post E" , According sun Doc SunSolve , there problem picker or Driver , I try move slot to slot successfully, On Lcd panel i can not see load drive (look like any inside tape in drive , but when i am select eject menu,... (0 Replies)
Discussion started by: hadibn
0 Replies
4. Solaris
In the /var/adm/messages, i am getting the following error :
Apr 16 23:49:37 inijsce1 EV_AGENT: Time Stamp 04/16/09 23:07:23 Event Number 2580 Severity Error Host inijscx33-adm Storage Array 6ASL102123 SP N/A SoftwareRev 6.19.1 (3.0) Unknown Error 2.19.0.300.5.027 Description Storage Array... (3 Replies)
Discussion started by: sundar3350
3 Replies
5. Solaris
Hi gurus
I don't understand the below messages as what is going on with my storage
Plz kindly suggest what could be the problem
Script started on Tue 12 May 2009 09:22:13 AM GMT
OMP-root-/salil> uptime
9:22am up 19:44, 2 users, load average: 0.10, 0.08, 0.08
OMP-root-/salil> uname -a... (4 Replies)
Discussion started by: girish.batra
4 Replies
6. AIX
Hi,
When I try to create a virtual disk in IVM ( integrated Virtual Machine VIO ) I get this message
Problems occurred while processing the data. A summary of all problems for this page are listed below. Additional details for each problem may be located next to the field causing the... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. AIX
Hello Everyone,
I am new to shell scripting and also i am very new to AIX machine
I have a question.
I have shell script which contains the follwing
"ps -e |grep $1
echo $2"
i run this schell script by doing this ./startSehllscript 3444 passed with two parameters .
Accroiding my... (4 Replies)
Discussion started by: swati
4 Replies
8. UNIX for Dummies Questions & Answers
People i have solaris 9 in a sparc platform i`m tryng to conect a stora edge a5100.When i do a format i don't see the disk, later i do a touch /reconfigure reboot and nothing cant anybody help me?
thank you (4 Replies)
Discussion started by: enkei17
4 Replies
LEARN ABOUT DEBIAN
perl::critic::policy::variables::prohibitpackagevars
Perl::Critic::Policy::Variables::ProhibitPackageVars(3pmUser Contributed Perl DocumentatiPerl::Critic::Policy::Variables::ProhibitPackageVars(3pm)
NAME
Perl::Critic::Policy::Variables::ProhibitPackageVars - Eliminate globals declared with "our" or "use vars".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Conway suggests avoiding package variables completely, because they expose your internals to other packages. Never use a package variable
when a lexical variable will suffice. If your package needs to keep some dynamic state, consider using an object or closures to keep the
state private.
This policy assumes that you're using "strict vars" so that naked variable declarations are not package variables by default. Thus, it
complains you declare a variable with "our" or "use vars", or if you make reference to variable with a fully-qualified package name.
$Some::Package::foo = 1; # not ok
our $foo = 1; # not ok
use vars '$foo'; # not ok
$foo = 1; # not allowed by 'strict'
local $foo = 1; # bad taste, but technically ok.
use vars '$FOO'; # ok, because it's ALL CAPS
my $foo = 1; # ok
In practice though, its not really practical to prohibit all package variables. Common variables like $VERSION and @EXPORT need to be
global, as do any variables that you want to Export. To work around this, the Policy overlooks any variables that are in ALL_CAPS. This
forces you to put all your exported variables in ALL_CAPS too, which seems to be the usual practice anyway.
CONFIGURATION
There is room for exceptions. Some modules, like the core File::Find module, use package variables as their only interface, and others
like Data::Dumper use package variables as their most common interface. These module can be specified from your .perlcriticrc file, and
the policy will ignore them.
[Variables::ProhibitPackageVars]
packages = Data::Dumper File::Find FindBin Log::Log4perl
This is the default setting. Using "packages =" will override these defaults.
You can also add packages to the defaults like so:
[Variables::ProhibitPackageVars]
add_packages = My::Package
You can add package "main" to the list of packages, but that will only OK variables explicitly in the "main" package.
SEE ALSO
Perl::Critic::Policy::Variables::ProhibitPunctuationVars
Perl::Critic::Policy::Variables::ProhibitLocalVars
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.14.2 2012-06-07 Perl::Critic::Policy::Variables::ProhibitPackageVars(3pm)