Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Agent Installation Issue on Ops Center Post 302759269 by DukeNuke2 on Tuesday 22nd of January 2013 02:26:39 AM
Old 01-22-2013
on which hardware?
 

7 More Discussions You Might Find Interesting

1. Solaris

Sun xVM Ops Center 1.1

I have 180 Solaris 7, 8 and 9 servers to patch and am looking at using xVM Ops Center. Has anyone here had any experience with it? (1 Reply)
Discussion started by: mr_crosby
1 Replies

2. Solaris

Sun Ops Center

Hi, Can anyone share the link to download sun ops centre i have sun partner account, but i unable find the link Thanks RJS (3 Replies)
Discussion started by: rajasekg
3 Replies

3. Solaris

OPS Center Email Notifications

Hi, Does any one know how to configure email notifications (to exchange) in Oracle Enterprise Manager 11g OPS Center? I have gone through the documentation and have done everything it asked, but still no notifications via email. I get the following error: At the OS level i tried sending email... (20 Replies)
Discussion started by: Mack1982
20 Replies

4. UNIX and Linux Applications

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

5. AIX

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

6. UNIX for Advanced & Expert Users

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

7. Solaris

Ops Center AI wrong IP

Hello, I have problems with Automated Installer on Solaris 11. I tried provision Solaris 11 on my T5-1B server from Ops Center, but AI set wrong IP address for manifest SMF. My Ops Center server has two IP addresses 10.236.102.219 and 10.226.21.141. Second IP is in subnet for provisioning of... (25 Replies)
Discussion started by: olibertu
25 Replies
ddi_intr_get_supported_types(9F)										  ddi_intr_get_supported_types(9F)

NAME
ddi_intr_get_supported_types - return information on supported hardware interrupt types SYNOPSIS
#include <sys/types.h> #include <sys/conf.h> #include <sys/ddi.h> #include <sys/sunddi.h> int ddi_intr_get_supported_types(dev_info_t *dip, int *typesp); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) dip Pointer to dev_info structure typesp Pointer to supported interrupt types The ddi_intr_get_supported_types() function retrieves the interrupt types supported by a particular hardware device and by the system soft- ware. Upon successful return, the supported types are returned as a bit mask in the integer pointed to by the typesp argument. See <sys/ddi_intr.h> for a list of interrupts that can be returned by a hardware device. For PCI devices that support MSI and/or MSI-X based hardware, this interface returns only the interrupt types that are supported by all the hardware in the path to the hardware device. An interrupt type is usable by the hardware device if it is returned by the ddi_intr_get_supported_types() function. The device driver can be programmed to use one of the returned interrupt types to receive hardware interrupts. The ddi_intr_get_supported_types() function returns: DDI_SUCCESS On success. DDI_EINVAL On encountering invalid input parameters. DDI_INTR_NOTFOUND Returned when the hardware device is found not to support any hardware interrupts. CONTEXT
The ddi_intr_get_supported_types() function can be called from user or kernel non-interrupt context. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ pci(4), attributes(5), pcmcia(7D), sysbus(4), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_enable(9F) The ddi_intr_get_supported_types() function can be called by the device driver even at any time if the driver has added an interrupt han- dler for a given interrupt type. Soft interrupts are always usable and are not returned by this interface. Any consumer of this interface should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could result in inconsistent behavior among platforms. 07 Apr 2005 ddi_intr_get_supported_types(9F)
All times are GMT -4. The time now is 09:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy