11-18-2009
I want a HP-UX ENV,how could I?
just for practice,
10 More Discussions You Might Find Interesting
1. Solaris
hey guys!!!!
i have a few question .. how to modify the user ENV in Sun Solaris 10 ... Thanks!!!! (1 Reply)
Discussion started by: giancarlodjabon
1 Replies
2. Shell Programming and Scripting
Hello friends,
i run two scripts manually & they work.
i run them in cron & they don work.
how to match the two env's
1.command line env
2.cron env
i would like cron to use command line env.
Thanks & Regards
Abhijeet (1 Reply)
Discussion started by: abhijeetkul
1 Replies
3. Shell Programming and Scripting
Hi,
I want to check the path set for a particular variable.Like when i use "env" command ,so many variables are there.I have to search for that variable which i need.Instead can i have any cmd which i can directly check the path set for that variable except "echo $path_name"
Thanks,
... (3 Replies)
Discussion started by: rrs
3 Replies
4. Programming
Do you know shell in Linux without HOME env.
Best regards,
Iliyan Varshilov (1 Reply)
Discussion started by: ilko_partizan
1 Replies
5. Shell Programming and Scripting
Hi,
I want to get the value of the env varables using the ksh script. All the env variables are stored in a file.
Eg.
file1
$INPATH
$OUTPATH
myscirpt:
for name in `awk { print $1 } file1`
do
cd $name
done
i'm getting the error like $INPATH not found.
in the same script... (1 Reply)
Discussion started by: vij_krr
1 Replies
6. Shell Programming and Scripting
All,
what is env command used for in Unix?
Regards
Oracle User (2 Replies)
Discussion started by: Oracle_User
2 Replies
7. Solaris
What is the difference between ${variable} and $variable when used in a script? (2 Replies)
Discussion started by: orange47
2 Replies
8. Red Hat
i have a file that i need to edit and replace a single value with another. so i have two variables, $oldvalue and $newvalue but below doesn't work:
ed file.txt << EOF
,s/$oldversion/$newversion/g
wq
EOFi presume it's the $ that is the issue since it's actually special to ed. any suggestions?... (1 Reply)
Discussion started by: crimso
1 Replies
9. Web Development
(Above from Apache docs).
On my system, using:
SetEnvIf User-Agent Mozilla IsBad=1
Order allow,deny
Allow from all
Deny from env=IsBad ...I see that environment variable is set (using phpinfo()) but the page is still served. No errors in the Apache logs. (1 Reply)
Discussion started by: gnurob
1 Replies
10. Red Hat
Hi,
I need to add file the /usr/lib under the command set. The /usr/lib need to be set under the DIRS=' ' while listing the set command.
I tried with the command below:
export PATH=${PATH}:/usr/bin
But this doesn't work out... (4 Replies)
Discussion started by: gsiva
4 Replies
LEARN ABOUT CENTOS
perl::critic::policy::variables::prohibitpackagevars
Perl::Critic::Policy::Variables::ProhibitPackageVars(3) User Contributed Perl DocumentationPerl::Critic::Policy::Variables::ProhibitPackageVars(3)
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.16.3 2014-06-09 Perl::Critic::Policy::Variables::ProhibitPackageVars(3)