03-10-2009
sorry, for the I/O error.....
ok.. did you power off the system and boot again?
were you able to probe the disk?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I connect to a Sun Box through telnet but it timed out in couple of minutes.
Advance thanks for any idea...help... (2 Replies)
Discussion started by: s_aamir
2 Replies
2. UNIX for Dummies Questions & Answers
Hello,
How can I set up events to be executed at a certain time? And do I need some kind of privilege such as being in cron group? (2 Replies)
Discussion started by: rayne
2 Replies
3. HP-UX
I am trying to connect with my hp machine using "dialup networking." It times out after 30 seconds. Is there a way to adjust this time. Would it have anything to do with rexec?
thanks (0 Replies)
Discussion started by: paschal
0 Replies
4. Programming
Is there any way in which I can make my wait signal to wait for a specified time for child job to complete. And if that time is over, the program gets out of the wait signal to process other things (4 Replies)
Discussion started by: anjul_thegreat
4 Replies
5. Shell Programming and Scripting
Hello,
I would like to make a script, ideally in perl since I am most familair with it, that does the following:
automatically starts up at 9 pm, searches through a specified directory for any new files, finds those new files and starts to run them through a pipeline. I have most of it worked... (4 Replies)
Discussion started by: amcrisan
4 Replies
6. Solaris
I HAVE A PERL SCRIPT WHICH RCP files from one server to another. The script is not having any issues for years and it is running for more than 3 years . Last week it had failed with error "Command timed out " error. Please help me out (3 Replies)
Discussion started by: praviper
3 Replies
7. Shell Programming and Scripting
Hi all
I need a little bit of help, i am looking for a script that can have different events in it and then if it is a certain day email me about it
some sort of email reminder system
any ideas
thanks (4 Replies)
Discussion started by: ab52
4 Replies
8. Shell Programming and Scripting
I want to warn everyone, I am not a programmer lol. I'm an IT wanting to get a little insight of programming, and I like to play around so I can learn. Ok, so I'm going to school for IT Security and Forensics. I had a project to write a hack, and I chose to write a shell script to run dd to write... (8 Replies)
Discussion started by: joshbgosh10592
8 Replies
9. Emergency UNIX and Linux Support
This has never happened before, but my laptop is now unable to access any remote servers. I have tried with 3 independent servers that I have access as recently as last week.
I am not asked for my password,
home:~ x$ ssh -v -p22 user@server
OpenSSH_5.2p1, OpenSSL 0.9.7l 28 Sep 2006... (17 Replies)
Discussion started by: chrisjorg
17 Replies
10. AIX
Hello,
I have two AIX6.1 machines that can communicate with each other through ssh.
The problem is that one of them somehow closes the connection after some time and i don't know the reason of that.
For example today i send through rsync command 7 files from one server to the other. It send... (7 Replies)
Discussion started by: omonoiatis9
7 Replies
probe(9E) Driver Entry Points probe(9E)
NAME
probe - determine if a non-self-identifying device is present
SYNOPSIS
#include <sys/conf.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
static intprefixprobe(dev_info_t *dip);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required for non-self-identifying devices. You must write it for such devices. For
self-identifying devices, nulldev(9F) should be specified in the dev_ops(9S) structure if a probe routine is not necessary.
ARGUMENTS
dip Pointer to the device's dev_info structure.
DESCRIPTION
probe() determines whether the device corresponding to dip actually exists and is a valid device for this driver. probe() is called after
identify(9E) and before attach(9E) for a given dip. For example, the probe() routine can map the device registers using ddi_map_regs(9F)
then attempt to access the hardware using ddi_peek(9F) or ddi_poke(9F) and determine if the device exists. Then the device registers
should be unmapped using ddi_unmap_regs(9F).
To probe a device that was left powered off after the last detach(), it might be necessary to power it up. If so, the driver must power up
the device by accessing device registers directly. pm_raise_power(9F) will be not be available until attach(9E). The framework ensures
that the ancestors of the node being probed and all relevant platform-specific power management hardware is at full power at the time that
probe() is called.
probe() should only probe the device. It should not change any software state and should not create any software state. Device initializa-
tion should be done in attach(9E).
For a self-identifying device, this entry point is not necessary. However, if a device exists in both self-identifying and non-self-iden-
tifying forms, a probe() routine can be provided to simplify the driver. ddi_dev_is_sid(9F) can then be used to determine whether probe()
needs to do any work. See ddi_dev_is_sid(9F) for an example.
RETURN VALUES
"small and bold">DDI_PROIf_theCprobe was successful.
DDI_PROBE_FAILURE If the probe failed.
DDI_PROBE_DONTCARE If the probe was unsuccessful, yet attach(9E) should still be called.
DDI_PROBE_PARTIAL If the instance is not present now, but may be present in the future.
SEE ALSO
attach(9E), identify(9E), ddi_dev_is_sid(9F), ddi_map_regs(9F), ddi_peek(9F), ddi_poke(9F), nulldev(9F), dev_ops(9S)
Writing Device Drivers
SunOS 5.10 18 Nov 1992 probe(9E)