Sponsored Content
Operating Systems Solaris sun 8 unable to communicate through console Post 302261712 by incredible on Tuesday 25th of November 2008 11:29:59 AM
Old 11-25-2008
You may try using the Serial B at the server end or use a Tera Term instead of Hyperterminal
 

9 More Discussions You Might Find Interesting

1. Solaris

Hooking up to Console's on sun's

it there any docs out there anyhwre that have the specs for cabing to a sun console. I have an e420 here, i cant seem to get a console connection, i have triewd the silver serial connectors that come with the new dsun servers, but no luck with those. (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. HP-UX

Unable to login at console and telnet

Hi friend, I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var? thanks. vestro (1 Reply)
Discussion started by: vestro
1 Replies

3. Red Hat

unable to communicate with Linux machine

Hi all, I installed red hat 2.6.9-5 and when I am trying to ping it.I am able to ping any other machine in the network but unable to do vice-versa(means unable to ping this machine from any other machine) and getting the message -- please provide your valuable suggestions ... (2 Replies)
Discussion started by: smartgupta
2 Replies

4. Infrastructure Monitoring

unable to load console info in SUNMC 4.0

hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. plz try to solve the problem Regards spandhan (5 Replies)
Discussion started by: spandhan
5 Replies

5. Solaris

unable to load console info in SUNMC 4.0

Hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. Iam using M9000 server solaris 10 plz try to solve the problem Regards spandhan (0 Replies)
Discussion started by: spandhan
0 Replies

6. Solaris

Sun Fire V890 - Unable to access RSC or Serial console

Hello Folks, I am having trouble to login to rsc or serial console of V890. The rsc2.2.3 has been configured with required parameters, resetrs and even rebooted. When serial port is connected to laptop, The hyper terminal does not get the console or POSt messages when the server is rebooting... (8 Replies)
Discussion started by: defflepord
8 Replies

7. AIX

P550 Unable to access Console

I have recently aquired the following machine: IBM,9113-550 Up until yesterday we could connect a dumb terminal to serial port 1 and get console login. However the dumb terminal died. We are now using a laptop with a null modem cable attached to serial port 1. This works perfectly for all of... (1 Reply)
Discussion started by: rsw7724
1 Replies

8. Solaris

Unable to take console

When trying to connect to console, I am getting the below error. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. plathwsvcd: Another instance is running. INIT: Id "plhw" respawning too fast: disabled for 5 minutes ... (3 Replies)
Discussion started by: aksijain
3 Replies

9. Solaris

Unable to start webconsole:console

Here is issue... bash-3.00# svcs system/webconsole:console STATE STIME FMRI maintenance 1:15:54 svc:/system/webconsole:console bash-3.00# svcadm clear svc:/system/webconsole:console bash-3.00# svcs -a |grep /system/webconsole offline* 1:20:44... (0 Replies)
Discussion started by: lingeshwaran
0 Replies
Devel::REPL::Plugin::ReadLineHistory(3pm)		User Contributed Perl Documentation		 Devel::REPL::Plugin::ReadLineHistory(3pm)

NAME
Devel::REPL::Plugin::ReadLineHistory - Integrate history with the facilities provided by Term::ReadLine DESCRIPTION
This plugin enables loading and saving command line history from a file as well has history expansion of previous commands using the !-syntax a la bash. By default, history expansion is enabled with this plugin when using Term::ReadLine::Gnu. That means that "loose" '!' characters will be treated as history events which may not be what you wish. To avoid this, you need to quote the '!' with '': my $var = "foo!"; or place the arguments in single quotes---but enable the "Term::ReadLine" attribute "history_quotes_inhibit_expansion": $_REPL->term->Attribs->{history_quotes_inhibit_expansion} = 1; my $var = 'foo!'; and to disable history expansion from GNU readline/history do $_REPL->term->Attribs->{do_expand} = 0; CONFLICTS
Note that Term::ReadLine::Perl does not support a history expansion method. In that case, you may wish to use the Devel::REPL History plugin which provides similar functions. Work is underway to make use of either History or ReadLineHistory consistent for expansion with either the Term::ReadLine::Gnu support or Term::ReadLine::Perl. perl v5.14.2 2010-06-13 Devel::REPL::Plugin::ReadLineHistory(3pm)
All times are GMT -4. The time now is 10:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy