08-09-2018
This stuff is really easy if you just slow down a bit and read the instructions.
It's hard to believe, I know.. but it's actually faster to do it slower, LOL
10 More Discussions You Might Find Interesting
1. HP-UX
Hi
I have been asked to find out how to
1) create users
2) reset passwords
3) kill processes that may require root privileges
without having root password, sudo rights or rights to passwd command
Any ideas?
Thanks in advance (1 Reply)
Discussion started by: emealogistics
1 Replies
2. Programming
Hi,
I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines.
I receive a 'EFAULT' when I try to access /dev/mem on these servers.
I suspect some... (1 Reply)
Discussion started by: ragisreekanth
1 Replies
3. Solaris
Dear
i have installed Solaris 10 on SUN V240
after installation i can not access system through root user
if i access system through any other user it conects but root is not connecting through LAN
if i connect through SC and then access root though cosole -f command it also works
kindly... (6 Replies)
Discussion started by: rizwan225
6 Replies
4. Shell Programming and Scripting
Hi,
I need to access a user's command history. However, the dilemma is that he is logged in and so his current history is not yet flushed to .bash_history file which gets flushed when he logs out. Is there a way I can still access his most recent history?
thank you,
S (4 Replies)
Discussion started by: sardare
4 Replies
5. Solaris
Please let me know how to setup a non-root user to be able to access a privileged port (<1024) on Solaris 8. I am currently running tomcat as "tomcat" user and I get the following error during to start up:
SEVERE: Error initializing endpoint
java.net.BindException: Permission denied<null>:443 (5 Replies)
Discussion started by: pingmeback
5 Replies
6. UNIX for Dummies Questions & Answers
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies
7. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 Replies
8. UNIX for Advanced & Expert Users
Hello Gurus,
I want One user to su to another without allowing root access and password.
I want to run a specific command as below from user am663:
---------------------------------------------------------
sudo -u appsprj4 /home/appsrj4/scripts/start_apache.sh
-------------------
But... (6 Replies)
Discussion started by: pokhraj_d
6 Replies
9. Solaris
Hello,
It is Solaris-10. There is a file as /opt/vpp/dom1.2/pdd/today_23. It is always generated by root, so owned by root only.
This file has to be deleted as part of application restart always and that is done by app_user and SA is always involved to do rm on that file.
Is it possible to give... (9 Replies)
Discussion started by: solaris_1977
9 Replies
10. AIX
greetings, just ran across a fun situation we had overlooked.
We have a backdoor user, no special privileges, which we put on every server so that anyone in the shop can get in (passwd in vault) if they need to, even if they don't have a local account on that server. The point of course is to... (3 Replies)
Discussion started by: maraixadm
3 Replies
LEARN ABOUT MOJAVE
moose::cookbook::snack::keywords5.18
Moose::Cookbook::Snack::Keywords(3) User Contributed Perl Documentation Moose::Cookbook::Snack::Keywords(3)
NAME
Moose::Cookbook::Snack::Keywords - Restricted "keywords" in Moose
VERSION
version 2.1202
DESCRIPTION
Moose exports a number of sugar functions in order to emulate Perl built-in keywords. These can cause clashes with other user-defined
functions. This document provides a list of those keywords for easy reference.
The 'meta' keyword
"use Moose" adds a method called "meta" to your class. If this conflicts with a method or function you are using, you can rename it, or
prevent it from being installed entirely. To do this, pass the "-meta_name" option when you "use Moose". For instance:
# install it under a different name
use Moose -meta_name => 'moose_meta';
# don't install it at all
use Moose -meta_name => undef;
Moose Keywords
If you are using Moose or Moose::Role it is best to avoid these keywords:
extends
with
has
before
after
around
super
override
inner
augment
confess
blessed
Moose::Util::TypeConstraints Keywords
If you are using Moose::Util::TypeConstraints it is best to avoid these keywords:
type
subtype
class_type
role_type
maybe_type
duck_type
as
where
message
inline_as
coerce
from
via
enum
find_type_constraint
register_type_constraint
Avoiding collisions
Turning off Moose
To remove the sugar functions Moose exports, just add "no Moose" at the bottom of your code:
package Thing;
use Moose;
# code here
no Moose;
This will unexport the sugar functions that Moose originally exported. The same will also work for Moose::Role and
Moose::Util::TypeConstraints.
Sub::Exporter features
Moose, Moose::Role and Moose::Util::TypeConstraints all use Sub::Exporter to handle all their exporting needs. This means that all the
features that Sub::Exporter provides are also available to them.
For instance, with Sub::Exporter you can rename keywords, like so:
package LOL::Cat;
use Moose 'has' => { -as => 'i_can_haz' };
i_can_haz 'cheeseburger' => (
is => 'rw',
trigger => sub { print "NOM NOM" }
);
LOL::Cat->new->cheeseburger('KTHNXBYE');
See the Sub::Exporter docs for more information.
namespace::autoclean and namespace::clean
You can also use namespace::autoclean to clean up your namespace. This will remove all imported functions from your namespace. Note that
if you are importing functions that are intended to be used as methods (this includes overload, due to internal implementation details), it
will remove these as well.
Another option is to use namespace::clean directly, but you must be careful not to remove "meta" when doing so:
package Foo;
use Moose;
use namespace::clean -except => 'meta';
# ...
SEE ALSO
Moose
Moose::Role
Moose::Util::TypeConstraints
Sub::Exporter
namespace::autoclean
namespace::clean
AUTHORS
o Stevan Little <stevan.little@iinteractive.com>
o Dave Rolsky <autarch@urth.org>
o Jesse Luehrs <doy@tozt.net>
o Shawn M Moore <code@sartak.org>
o XXXX XXX'XX (Yuval Kogman) <nothingmuch@woobling.org>
o Karen Etheridge <ether@cpan.org>
o Florian Ragwitz <rafl@debian.org>
o Hans Dieter Pearcey <hdp@weftsoar.net>
o Chris Prather <chris@prather.org>
o Matt S Trout <mst@shadowcat.co.uk>
COPYRIGHT AND LICENSE
This software is copyright (c) 2006 by Infinity Interactive, Inc..
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.18.2 2014-01-19 Moose::Cookbook::Snack::Keywords(3)