06-13-2005
yes, i think this will work fine. Thanks for your help.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I work on some hp ux 11.00 Servers. i have to add an user. i use the useradd command like follows: useradd -u 72022 -g 71095 -c " comment " -d /PACKAGE_NAME/home/username -s /usr/bin/sh username
The command returns with error 3. The manpage means value number 3: Invalid argument supplied to an... (6 Replies)
Discussion started by: ortsvorsteher
6 Replies
2. UNIX for Advanced & Expert Users
Hi.
due to some needs i gave a user the premission to use useradd command with sudo.
i want to know if there is a way to let him set the initial password, without giving him the premission to use passwd command as root (sudo).
maybe a way to set a default password for all the new users that... (2 Replies)
Discussion started by: dorilevy
2 Replies
3. Shell Programming and Scripting
Gurus,
I need to add a user to all the machines. I need a script to do this. I did one but it does not allow me to su to root within a ssh session i open. It exists saying su: Sorry. Please let me know how i can do it. I do not have the freedom of using sudo either.
Regards (4 Replies)
Discussion started by: earlysame55
4 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
when using useradd command, what are the necessary options/arguments to be included?
Please advice. (4 Replies)
Discussion started by: etcpasswd
4 Replies
5. Solaris
O/S: Solaris 9
Architecture: SPARC
The man page for useradd states, "The new login remains locked until the passwd(1) command is executed."
This is a problem for me when accessing remotely via SSH and creating a new account from the console with useradd. As soon as I try to login into the... (3 Replies)
Discussion started by: tuxsun1
3 Replies
6. Shell Programming and Scripting
Ok Im trying too make this shell script create users from my text file, I also want to type in a password for the new users. So thay can make a uniq one themself after first logon.
#!/bin/sh
# Sebastian schmidt
clear
echo "*************************************************************"... (3 Replies)
Discussion started by: chipmunken
3 Replies
7. BSD
hi..
i want to know when we add a new user by useradd command in linux "ram" in the system then bydefault " ram "
name directory will create inside /home/ram . why..??
i want to know behind this logic .
please help me. (1 Reply)
Discussion started by: rinkugarg
1 Replies
8. Solaris
if useradd command is deleted in solaris how do we add user (3 Replies)
Discussion started by: vivek_ng
3 Replies
9. Solaris
I want to creat a 27 logins in solaris.Can anyone tell me how to write a script for that so that i create at a time for all 27 people.
Thanks to guide me. (6 Replies)
Discussion started by: kkalyan
6 Replies
10. Shell Programming and Scripting
Hello,
I need ansible playbook to create new user on remote server. Remote server blocked direct root login so I must login first application user and later I must run "useradd" command with sudo.
I need playbook.yml and cli command.
Best regards, (0 Replies)
Discussion started by: getrue
0 Replies
LEARN ABOUT OSX
dbd::gofer::policy::base
DBD::Gofer::Policy::Base(3) User Contributed Perl Documentation DBD::Gofer::Policy::Base(3)
NAME
DBD::Gofer::Policy::Base - Base class for DBD::Gofer policies
SYNOPSIS
$dbh = DBI->connect("dbi:Gofer:transport=...;policy=...", ...)
DESCRIPTION
DBD::Gofer can be configured via a 'policy' mechanism that allows you to fine-tune the number of round-trips to the Gofer server. The
policies are grouped into classes (which may be subclassed) and referenced by the name of the class.
The DBD::Gofer::Policy::Base class is the base class for all the policy classes and describes all the individual policy items.
The Base policy is not used directly. You should use a policy class derived from it.
POLICY CLASSES
Three policy classes are supplied with DBD::Gofer:
DBD::Gofer::Policy::pedantic is most 'transparent' but slowest because it makes more round-trips to the Gofer server.
DBD::Gofer::Policy::classic is a reasonable compromise - it's the default policy.
DBD::Gofer::Policy::rush is fastest, but may require code changes in your applications.
Generally the default "classic" policy is fine. When first testing an existing application with Gofer it is a good idea to start with the
"pedantic" policy first and then switch to "classic" or a custom policy, for final testing.
POLICY ITEMS
These are temporary docs: See the source code for list of policies and their defaults.
In a future version the policies and their defaults will be defined in the pod and parsed out at load-time.
See the source code to this module for more details.
POLICY CUSTOMIZATION
XXX This area of DBD::Gofer is subject to change.
There are three ways to customize policies:
Policy classes are designed to influence the overall behaviour of DBD::Gofer with existing, unaltered programs, so they work in a
reasonably optimal way without requiring code changes. You can implement new policy classes as subclasses of existing policies.
In many cases individual policy items can be overridden on a case-by-case basis within your application code. You do this by passing a
corresponding "<go_<policy_name">> attribute into DBI methods by your application code. This let's you fine-tune the behaviour for special
cases.
The policy items are implemented as methods. In many cases the methods are passed parameters relating to the DBD::Gofer code being
executed. This means the policy can implement dynamic behaviour that varies depending on the particular circumstances, such as the
particular statement being executed.
AUTHOR
Tim Bunce, <http://www.tim.bunce.name>
LICENCE AND COPYRIGHT
Copyright (c) 2007, Tim Bunce, Ireland. All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.
perl v5.16.2 2007-10-16 DBD::Gofer::Policy::Base(3)