02-14-2010
All these command don't help.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I was trying to test run a /bin/bash script i had just written when my monitor suddenly went blank.I had to shut down the machine from the systems main power. I was unable to boot afterwards and soo i went for the interactive boot process by typing boot -a.
I succeded in the first stage of the... (1 Reply)
Discussion started by: lealyz
1 Replies
2. UNIX for Dummies Questions & Answers
I have a Sun box that I am trying to get started up, but everytime it will crap out because it is bound to an NIS domain that no longer exists. The Master for that domain was put out of commission. It was suggested to me that I could boot off of the Installation cd for the OS (Solaris 8) and... (4 Replies)
Discussion started by: Jody
4 Replies
3. Solaris
Hi,
I have a Sun 3500 server on which i installed solaris 8 and have also installed veritas 4.0 on it. i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.... i have got to connect a laptop to the serial port of the server and... (3 Replies)
Discussion started by: ishila
3 Replies
4. Solaris
Hello
I have Sun Ultra 10 with Solaris 7 installed on it.
Sometimes back
after that the machine use to get hang .Even after
rebooting the system was not booting.
I have manually switch on /off many times from the
power board itself .Once in a while it
use to boot .After... (12 Replies)
Discussion started by: turki_00
12 Replies
5. Solaris
Hi,
I have a sun ultra enterprise 450 server. This server powers on and a white screen appears with the system and network information.
But it doesnot boot up completely. Booting operation wil be halted by a warning:
\usr\sbin\fsck not found. Most likely the mount of \usr failed or the... (5 Replies)
Discussion started by: tgashwini
5 Replies
6. Solaris
Got the console cable all connected up and got tot he ok prompt.
Typed in boot cdrom and got the following:
ok boot cdrom
Boot device: /pci@8,700000/scsi@6/disk@6,0:f File and args:
ERROR: /packages/deblocker: Last Trap: Corrected ECC Error
Can't read disk label.
Can't open disk... (4 Replies)
Discussion started by: bbbngowc
4 Replies
7. Solaris
Hi all,
I am getting boot time message for sun E420R server. I need urgent help.
Hardware Power ON
CPU Offline (not present)
Master CPU : 0000.0001.0055.11a0
CPU Offline (not present)
CPU Offline (not present)
Master E$ : 0000.0000.0040.0000
Button Power ON (0 Replies)
Discussion started by: PUSHPARAJA
0 Replies
8. Solaris
Sun Fire V210, No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.13.2, 4096 MB memory installed, Serial #61203679.
Ethernet address 0:3:ba:a5:e4:df, Host ID: 83a5e4df.
Boot device: net File and args:
100 Mbps FDX Link up
Timeout waiting for... (5 Replies)
Discussion started by: Mrudhul
5 Replies
9. Solaris
Booting problem on Sun 3500
Hi,
I have a Sun 3500 server on which i installed solaris 5.2 installed . i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.i got a message Sync file system than restart
some times showing ok... (2 Replies)
Discussion started by: najeer
2 Replies
10. Solaris
Hello
I have an old sun fire v250 server that I am trying to revive.
I am trying to boot it from cdrom to install the OS (Solaris 10). The original data in the disk is corrupt and I am trying to do a new clean install. However I encounter the following errors.
Does it look like the disk itself... (1 Reply)
Discussion started by: br1an
1 Replies
LEARN ABOUT DEBIAN
event::rpc::loop
Event::RPC::Loop(3pm) User Contributed Perl Documentation Event::RPC::Loop(3pm)
NAME
Event::RPC::Loop - Mainloop Abstraction layer for Event::RPC
SYNOPSIS
use Event::RPC::Server;
use Event::RPC::Loop::Glib;
my $server = Event::RPC::Server->new (
...
loop => Event::RPC::Loop::Glib->new(),
...
);
$server->start;
DESCRIPTION
This modules defines the interface of Event::RPC's mainloop abstraction layer. It's a virtual class all mainloop modules should inherit
from.
INTERFACE
The following methods need to be implemented:
$loop->enter ()
Enter resp. start a mainloop.
$loop->leave ()
Leave the mainloop, which was started with the enter() method.
$watcher = $loop->add_io_watcher ( %options )
Add an I/O watcher. Options are passed as a hash of key/value pairs. The following options are known:
fh The filehandle to be watched.
cb This callback is called, without any parameters, if an event occured on the filehandle above.
desc
A description of the watcher. Not necessarily implemented by all modules, so it may be ignored.
poll
Either 'r', if your program reads from the filehandle, or 'w' if it writes to it.
A watcher object is returned. What this exactly is depends on the implementation, so you can't do anything useful with it besides
passing it back to del_io_watcher().
$loop->del_io_watcher ( $watcher )
Deletes an I/O watcher which was added with $loop->add_io_watcher().
$timer = $loop->add_timer ( %options )
This sets a timer, a subroutine called after a specific timeout or on a regularly basis with a fixed time interval.
Options are passed as a hash of key/value pairs. The following options are known:
interval
A time interval in seconds, may be fractional.
after
Callback is called once after this amount of seconds, may be fractional.
cb The callback.
desc
A description of the timer. Not necessarily implemented by all modules, so it may be ignored.
A timer object is returned. What this exactly is depends on the implementation, so you can't do anything useful with it besides passing
it back to del_io_timer().
$loop->del_timer ( $timer )
Deletes a timer which was added with $loop->add_timer().
DIRECT USAGE IN YOUR SERVER
You may use the methods of Event::RPC::Loop by yourself if you like. This way your program keeps independent of the actual mainloop module
in use, if the simplified interface of Event::RPC::Loop is sufficient for you.
In your server program you access the actual mainloop object this way:
my $loop = Event::RPC::Server->instance->get_loop;
Naturally nothing speaks against making your program to work only with a specific mainloop implementation, if you need its features. In
that case you may use the corresponding API directly (e.g. of Event or Glib), no need to access it through Event::RPC::Loop.
AUTHORS
Joern Reder <joern at zyn dot de>
COPYRIGHT AND LICENSE
Copyright (C) 2002-2006 by Joern Reder, All Rights Reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2006-04-23 Event::RPC::Loop(3pm)