12-26-2017
You tell us that you have a function that has worked in the future (although I don't know what time machine you used to determine that) and that it doesn't work now. But, you:
haven't told us:
- what interpreter is used to run this code,
- what it does when it worked correctly in the future,
- what it is doing now that is incorrect,
- what diagnostic messages it now produces, nor
- what normal outputs it now produces.
Without this basic information, it is hard for us to make any guesses as to why it doesn't work now but will work in the future!
10 More Discussions You Might Find Interesting
1. AIX
How to disable user for cd to some another folders other than his folders.
AIX 5L 5.2
Thanks
Dilip. (1 Reply)
Discussion started by: Dilippatel
1 Replies
2. UNIX for Dummies Questions & Answers
Hi. I have a situation here where I need to backup a users' home directory and restore onto another server. The issue here is that both servers have different operating systems and I am looking for advices on how to proceed.
The source server operating system is Tru64 v5.1, and here's the output... (1 Reply)
Discussion started by: fidodido
1 Replies
3. UNIX for Dummies Questions & Answers
Hi All ,
Some of the users should be restricted using the MV commands on some of the standard folders. We had an issue the other day like from the standard folder structure which was set up one of the user has moved a folder to a different location and the jobs failed as the folder was not... (6 Replies)
Discussion started by: perlamohan
6 Replies
4. AIX
I am starting to accumulate a few scripts that I working on to replace operational scripts and to have a few for my personal usage. I am not an admin, just an operator.
They are currently located inside the /tmp folder. I know they should not be there but since we have no system admin (someone... (4 Replies)
Discussion started by: Browser_ice
4 Replies
5. UNIX for Dummies Questions & Answers
Can some one help me with this issue . I require to restrict a particular user to a particular folder alone when they log in. I dont want this particular user to come out of this folder.
Kindly help (7 Replies)
Discussion started by: kirbhas72
7 Replies
6. Solaris
Hi All,
I am trying to create a folder in /export/home/user1 directory as a user1 but I am getting the error message as
-bash-3.00$ mkdir abc
mkdir: Failed to make directory "abc"; Permission denied
Also I tried creating the folder but it fails too
-bash-3.00$ touch abc
touch: cannot... (2 Replies)
Discussion started by: Manjunath K V
2 Replies
7. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
8. HP-UX
Hi Experts,
When i taking backup of my servers in Tape Library simultaneously the Temp folder is getting full...... these file like OB2DBG*.txt (2 Replies)
Discussion started by: purushottamaher
2 Replies
9. Shell Programming and Scripting
Hello All,
I have to write a shell script and use it in informatica. The script has to perform below actions:
The script gets executed from edw user.
Through the script, a DT folder has to be created under edw_sca user.
Is this scenario possible through a SHELL script or not.
... (2 Replies)
Discussion started by: bghosh
2 Replies
10. Shell Programming and Scripting
How to create a shell script to create a folder by using the today's date to take backup using rsync command on every evening around 7 pm.
Kindly help.
Thanks.
To be more precise,
I want to create a script which matches the today's date with server's date format, if matches then creates the... (2 Replies)
Discussion started by: bakula10
2 Replies
lib(3pm) Perl Programmers Reference Guide lib(3pm)
NAME
lib - manipulate @INC at compile time
SYNOPSIS
use lib LIST;
no lib LIST;
DESCRIPTION
This is a small simple module which simplifies the manipulation of @INC at compile time.
It is typically used to add extra directories to perl's search path so that later "use" or "require" statements will find modules which are
not located on perl's default search path.
Adding directories to @INC
The parameters to "use lib" are added to the start of the perl search path. Saying
use lib LIST;
is almost the same as saying
BEGIN { unshift(@INC, LIST) }
For each directory in LIST (called $dir here) the lib module also checks to see if a directory called $dir/$archname/auto exists. If so
the $dir/$archname directory is assumed to be a corresponding architecture specific directory and is added to @INC in front of $dir.
lib.pm also checks if directories called $dir/$version and $dir/$version/$archname exist and adds these directories to @INC.
The current value of $archname can be found with this command:
perl -V:archname
The corresponding command to get the current value of $version is:
perl -V:version
To avoid memory leaks, all trailing duplicate entries in @INC are removed.
Deleting directories from @INC
You should normally only add directories to @INC. If you need to delete directories from @INC take care to only delete those which you
added yourself or which you are certain are not needed by other modules in your script. Other modules may have added directories which
they need for correct operation.
The "no lib" statement deletes all instances of each named directory from @INC.
For each directory in LIST (called $dir here) the lib module also checks to see if a directory called $dir/$archname/auto exists. If so
the $dir/$archname directory is assumed to be a corresponding architecture specific directory and is also deleted from @INC.
Restoring original @INC
When the lib module is first loaded it records the current value of @INC in an array @lib::ORIG_INC. To restore @INC to that value you can
say
@INC = @lib::ORIG_INC;
CAVEATS
In order to keep lib.pm small and simple, it only works with Unix filepaths. This doesn't mean it only works on Unix, but non-Unix users
must first translate their file paths to Unix conventions.
# VMS users wanting to put [.stuff.moo] into
# their @INC would write
use lib 'stuff/moo';
NOTES
In the future, this module will likely use File::Spec for determining paths, as it does now for Mac OS (where Unix-style or Mac-style paths
work, and Unix-style paths are converted properly to Mac-style paths before being added to @INC).
If you try to add a file to @INC as follows:
use lib 'this_is_a_file.txt';
"lib" will warn about this. The sole exceptions are files with the ".par" extension which are intended to be used as libraries.
SEE ALSO
FindBin - optional module which deals with paths relative to the source file.
PAR - optional module which can treat ".par" files as Perl libraries.
AUTHOR
Tim Bunce, 2nd June 1995.
"lib" is maintained by the perl5-porters. Please direct any questions to the canonical mailing list. Anything that is applicable to the
CPAN release can be sent to its maintainer, though.
Maintainer: The Perl5-Porters <perl5-porters@perl.org>
Maintainer of the CPAN release: Steffen Mueller <smueller@cpan.org>
COPYRIGHT AND LICENSE
This package has been part of the perl core since perl 5.001. It has been released separately to CPAN so older installations can benefit
from bug fixes.
This package has the same copyright and license as the perl core.
perl v5.16.2 2013-08-25 lib(3pm)