Hi,
Command "chfn" can be used to change finger information.. can anybody tell me how to unset i mean reset the same finger information.
Thanks in advance,
Chanakya (3 Replies)
Hi All,
May be this is a very simple question...
$ b=8
$ readonly b
$ echo $b
8
$ b=90
-bash: b: readonly variable
$ unset b
-bash: unset: b: cannot unset: readonly variable
I m not able to change the readonly mode of variable b
Please help me out..
Thanks
Nidhi (2 Replies)
Hi,
I am writing a BASH script. My questions regard deleting elements of arrays.
I have an array:
michael-browns-powerbook-g4-15:~ msb65$ test_array=(1 2 3 4)
michael-browns-powerbook-g4-15:~ msb65$ echo ${test_array}
1 2 3 4
To delete the second element of test_array I type:... (3 Replies)
As of Solaris 9,10 in /etc/system file I can comment the “set maxuprc” for the restriction.
But in Solaris zones how I can unset the variable “maxuprc” because /etc/system file is not there.
How I can proceed.
Regards,
Kalai (1 Reply)
can I use unset to unset all the variables in a shell sciprt?
VAR1=1
VAR2=2
VAR3=3
unset
whether this unset will afftect any system variables?
Thanks, (3 Replies)
Could someone please tell me how to unset your .bashrc? I have tried all of these. I can't find anything useful from google.
unset -f .bashrc
unset .bashrc (9 Replies)
I'm wondering, is the number of variables will affect execution time of my bash script or maybe affect the cpu workload, cpu memory, etc ?
If I create so many variables, should I unset each one of that variables after I used them or after I think they are no longer needed?
and if my script... (2 Replies)
I have a script with a $PASSWORD variable. I unset it right after using it, just to minimize the chance it could be left around for a snooper. That worked just fine... until I used a password with a value of "P@ssw0rd" Now, unset (even with -f, even with the variable enquoted) tells me: unset:... (1 Reply)
Hi all,
Does anyone know how to change PROC_MEM_RES?
We have a DB server with quite a few oracle instances (RAC) and we are getting critical alerts for PROC_MEM_RES.
Anyone know how to increase the current setting or what we should do about it?
Thanks in advance.
john (2 Replies)
Hi,
I have the following line in the script
unset _SET_ENV_AA
unset _SETENV
but where I can check the value for this environement variable (2 Replies)
Discussion started by: stew
2 Replies
LEARN ABOUT OSX
apache::testmm
Apache::TestMM(3) User Contributed Perl Documentation Apache::TestMM(3)NAME
Apache::TestMM - Provide MakeMaker Wrapper Methods
SYNOPSIS
require Apache::TestMM;
# import MY::test and MY::clean overrides for MM
Apache::TestMM->import(qw(test clean));
# parse command line args
Apache::TestMM::filter_args();
# autogenerate the script
Apache::TestMM::generate_script('t/TEST');
DESCRIPTION
"Apache::TestMM" provides wrappers for the "ExtUtils::MakeMaker" craft, making it easier to extend the autogenerated Makefile with
"Apache::Test".
FUNCTIONS
"import"
use Apache::TestMM qw(test clean);
or:
Apache::TestMM->import(qw(test clean));
Imports "MY::" overrides for the default "ExtUtils::MakeMaker" test and clean targets, as if you have defined:
sub MY::test {...}
sub MY::clean {...}
in Makefile.PL. "Apache::TestMM" does this for you so that these Makefile targets will run the Apache server and the tests for it, and
clean up after its mess.
"filter_args"
push @ARGV, '-apxs', $apxs_path;
Apache::TestMM::filter_args();
WriteMakefile(...);
When "WriteMakefile()" is called it parses @ARGV, hoping to find special options like "PREFIX=/home/stas/perl". "Apache::Test" accepts a
lot of configuration options of its own. When "Apache::TestMM::filter_args()" is called, it removes any "Apache::Test"-specific options
from @ARGV and stores them internally, so when "WriteMakefile()" is called they aren't in @ARGV and thus won't be processed by
"WriteMakefile()".
The options can be set when Makefile.PL is called:
% perl Makefile.PL -apxs /path/to/apxs
Or you can push them manually to @ARGV from the code:
push @ARGV, '-apxs', $apxs_path;
When:
Apache::TestMM::generate_script('t/TEST');
is called, "Apache::Test"-specific options extracted by "Apache::TestMM::filter_args()" are written to the autogenerated file. In our
example, the autogenerated t/TEST will include:
%Apache::TestConfig::Argv = qw(apxs /path/to/apxs);
which is going to be used by the "Apache::Test" runtime.
The other frequently used options are: "-httpd", telling where to find the httpd (usually when the "-apxs" option is not used),
"-libmodperl" to use a specific mod_perl shared object (if your mod_perl is built as DSO), "-maxclients" to change the default number of
the configured "MaxClients" directive, "-port" to start the server on a specific port, etc. To get the complete list of available
configuration options and their purpose and syntax, run:
% perl -MApache::TestConfig -le 'Apache::TestConfig::usage()'
You may wish to document some of these in your application's README file, especially the "-apxs" and "-httpd" options.
"generate_script"
Apache::TestMM::generate_script('t/TEST');
"generate_script()" accepts the name of the script to generate and will look for a template with the same name and suffix .PL. So in our
example it'll look for t/TEST.PL. The autogenerated script t/TEST will include the contents of t/TEST.PL, and special directives, including
any configuration options passed via "filter_args()" called from Makefile.PL, special fixup code, etc.
perl v5.16.2 2011-02-07 Apache::TestMM(3)