I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Folks - any advice on lp commands etc..
I dont use printers on solaris servers, neither do we have any installed but I need to know as much as possible for the solaris admin course...
Any advice on good sources of information for printing commands in general? (1 Reply)
Module::Install::Admin(3) User Contributed Perl Documentation Module::Install::Admin(3)NAME
Module::Install::Admin - Author-side manager for Module::Install
SYNOPSIS
In a Module::Install extension module:
sub extension_method {
my $self = shift;
$self->admin->some_method(@args);
}
As an one-liner:
% perl "-MModule::Install::Admin" -e'&some_method(@args);'
The two snippets above are really shorthands for
$some_obj->some_method(@args)
where $some_obj is the singleton object of a class under the "Module::Install::Admin::*" namespace that provides the method "some_method".
See "METHODS" for a list of built-in methods.
DESCRIPTION
This module implements the internal mechanism for initializing, including and managing extensions, and should only be of interest to
extension developers; it is never included under a distribution's inc/ directory, nor are any of the Module::Install::Admin::* extensions.
For normal usage of Module::Install, please see Module::Install and "COOKBOOK / EXAMPLES" in Module::Install instead.
Bootstrapping
When someone runs a Makefile.PL that has "use inc::Module::Install", and there is no inc/ in the current directory, Module::Install will
load this module bootstrap itself, through the steps below:
o First, Module/Install.pm is POD-stripped and copied from @INC to inc/. This should only happen on the author's side, never on the end-
user side.
o Reload inc/Module/Install.pm if the current file is somewhere else. This ensures that the included version of inc/Module/Install.pm is
always preferred over the installed version.
o Look at inc/Module/Install/*.pm and load all of them.
o Set up a "main::AUTOLOAD" function to delegate missing function calls to "Module::Install::Admin::load" -- again, this should only
happen at the author's side.
o Provide a "Module::Install::purge_self" function for removing included files under inc/.
METHODS SEE ALSO
Module::Install
AUTHORS
Audrey Tang <autrijus@autrijus.org>
COPYRIGHT
Copyright 2003, 2004 by Audrey Tang <autrijus@autrijus.org>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
See <http://www.perl.com/perl/misc/Artistic.html>
perl v5.16.3 2012-03-01 Module::Install::Admin(3)