10-27-2006
Are there any more useful error messages in the logfiles?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I knew it would happen sooner or later....
We have a requirement that specific individuals need "sudo root" authority. I knew it only a matter of time before someone decided to change the root password (at least they owned up to it).
Now the question is how can I grant all rights except... (4 Replies)
Discussion started by: scottsl
4 Replies
2. UNIX for Dummies Questions & Answers
Hello chiefs :)
I have a SUN Enterprise 250, running Solaris 8.5 - I have managed to be able to connect a dumb terminal to the box via a standard straight-through rj45 cable, to my ibm laptop. OK so Putty can connect to the box via ssh - nice! But I dont have the password for root - or any... (1 Reply)
Discussion started by: congo
1 Replies
3. Solaris
Any body pls let me know the procedure to recover ROOT password in Sun Netra 20 Server..I forgot the password. (5 Replies)
Discussion started by: gini
5 Replies
4. Solaris
I forget the Root Passwd of my Sun Netra 20 server and break the same by editing /etc/shadow.Now there is no passwd for Root.
And How to set new root passwd?Pls help.... (2 Replies)
Discussion started by: gini
2 Replies
5. UNIX for Dummies Questions & Answers
heyy
i forgot my root passwd but i cant reinstall due to some reason can anyone tell me hw to reterive root passwd (10 Replies)
Discussion started by: mightypp.nits
10 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
Today I faced a problem trying to log in as root. The output error is
cannot execute sh: No such file....
I doubted there is something wrong with shell interpreter which resides in /etc/passwd file for every user who logs in.
I checked and the line for root account was... (4 Replies)
Discussion started by: elthox
4 Replies
7. Red Hat
hi
i have a RHEL 4 and have forgot root passwd
tried to boot in by singel user and then changing the passwd but it's not letting me do that ......throwing some weird error as .......manipulation
i also tried to make a new user from CLI but even though it's not letting me in from that user as... (12 Replies)
Discussion started by: techbravo
12 Replies
8. Red Hat
I accidentally changed root shell from /bin/bash to bash in /etc/password, then logged out from root. Now I can't login as root and got "No shell" error, although I have root password. "su -f -s /bin/bash" command does NOT work. There is no GUI interface for this system.
My question: Do I have... (7 Replies)
Discussion started by: aixlover
7 Replies
9. HP-UX
Hi All
I had installed sudo in HP UX 11.3 and it is working fine but not able to make entry required to set permission similar to ROOT without using password (PASSWD) change option for define user in /etc/sudoers file
Please help if some know the syntex? :confused::wall: (2 Replies)
Discussion started by: deviltech
2 Replies
10. UNIX for Beginners Questions & Answers
i do not have root on a solairs 10 server , however i do have the root role, i was wondering if I can change the root password as a a role with the passwd command? I have not tried yet.
and do i have to use the # chgkey -p afterwards?
i need to patch is why i am asking.
thanks (1 Reply)
Discussion started by: goya
1 Replies
LEARN ABOUT DEBIAN
log::agent::channel::handle
Agent::Channel::Handle(3pm) User Contributed Perl Documentation Agent::Channel::Handle(3pm)
NAME
Log::Agent::Channel::Handle - I/O handle logging channel for Log::Agent
SYNOPSIS
require Log::Agent::Channel::Handle;
my $driver = Log::Agent::Channel::Handle->make(
-prefix => "prefix",
-stampfmt => "own",
-showpid => 1,
-handle => *FILE,
);
DESCRIPTION
The handle channel performs logging to an already opened I/O handle, along with the necessary prefixing and stamping of the messages.
The creation routine make() takes the following arguments:
"-handle" => handle
Specifies the I/O handle to use. It can be given as a GLOB reference, such as "*FILE", or as an "IO::Handle" object.
NOTE: Auto-flushing is not enabled on the handle. Even when the channel is closed, the handle is left as-is: we simply stop sending
log messages to it.
"-no_newline" => flag
When set to true, never append any "
" (on Unix) or "
" (on Windows) to log messages.
Internally, Log::Agent relies on the channel to delimit logged lines appropriately, so this flag is not used. However, it might be
useful for "Log::Agent::Logger" users.
Default is false, meaning newline markers are systematically appended.
"-no_prefixing" => flag
When set to true, disable the prefixing logic entirely, i.e. the following options are ignored completely: "-prefix", "-showpid",
"-no_ucfirst", "-stampfmt".
Default is false.
"-no_ucfirst" => flag
When set to true, don't upper-case the first letter of the log message entry when there's no prefix inserted before the logged line.
When there is a prefix, a ":" character follows, and therefore the leading letter of the message should not be upper-cased anyway.
Default is false, meaning uppercasing is performed.
"-prefix" => prefix
The application prefix string to prepend to messages.
"-showpid" => flag
If set to true, the PID of the process will be appended within square brackets after the prefix, to all messages.
Default is false.
"-stampfmt" => (name | CODE)
Specifies the time stamp format to use. By default, my "own" format is used. See Log::Agent::Stamping for a description of the
available format names.
You may also specify a CODE ref: that routine will be called every time we need to compute a time stamp. It should not expect any
parameter, and should return a string.
CAVEAT
Beware of chdir(). If your program uses chdir(), you should always specify logfiles by using absolute paths, otherwise you run the risk of
having your relative paths become invalid: there is no anchoring done at the time you specify them. This is especially true when
configured for rotation, since the logfiles are recreated as needed and you might end up with many logfiles scattered throughout all the
directories you chdir()ed to.
AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com>
SEE ALSO
Log::Agent::Logger(3), Log::Agent::Channel(3).
perl v5.10.0 2002-03-09 Agent::Channel::Handle(3pm)