10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
one of my machine ,does not boot!
check the pic and kindly help!
Thx in advance! (0 Replies)
Discussion started by: ahmedamer12
0 Replies
2. Solaris
My one Sun machine is not able to ssh another machine of Sun. Although I have configured the ssh successfully
( SunOS sunbox2 5.9 Generic_118558-34 sun4u sparc SUNW,Sun-Blade-2500 )
ERROR
bash-2.05# ssh sunbox2
/etc/ssh/ssh_config: line 34: Bad configuration option: PermitRootLogin... (0 Replies)
Discussion started by: z_haseeb
0 Replies
3. Shell Programming and Scripting
I have created a script file named 'start-jboss'
-------------------------------------------------
#!/bin/sh
# For starting Jboss
JAVA_HOME=/home/argole/jdk/jdk1.6.0_10
export JAVA_HOME
cd /home/argole/server/jboss-4.2.0.GA/bin
echo "Starting JBOSS server"
nohup ./run.sh -c... (25 Replies)
Discussion started by: shiraz
25 Replies
4. HP-UX
I use the uptime command,but
it only show how long system has been up
up 18 days
but I want the this format
machine boot time YYYY-MM-DD hh:mm:ss
does any command can get that or how to i use program to do this (6 Replies)
Discussion started by: alert0919
6 Replies
5. Solaris
Hi Experts,
I am new for solaris, i am using Solaris10,can you anyone assist me how to configure IP in my machine.
Thanks (4 Replies)
Discussion started by: daya.pandit
4 Replies
6. Solaris
During system startup the following warnings are appear.
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Connected command timeout for target 9.0
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Target 9 reducing sync, transfer rate
Warning: /pci@8, 700000/scsi@6, 1... (5 Replies)
Discussion started by: tabreaz
5 Replies
7. Solaris
I had one sun ultra enterprise1 cpu.
it's not giving any disply,which operating system it's support.
How can install os on this CPU. (2 Replies)
Discussion started by: jagadeesh
2 Replies
8. UNIX for Dummies Questions & Answers
I have a sun v240 running solaris 9. I recently changed the ip via the ifconfig command but made a mistake when running the command:
ifconfig bge0 (ip address) netmask (ip address)
when i meant to do:
ifconfig bge0 (ip address) netmask ffff0000 broadcast (ip address)
Now when I boot the... (4 Replies)
Discussion started by: GLJ@USC
4 Replies
9. UNIX for Dummies Questions & Answers
I'm in a predicament right now! I have RedHat 7.2 ,Debian 2.2r5 ,and Windows ME. I am currently in a Sun Solaris 8 class and will soon acquire a copy of Solaris 8. I would like to start a small home network ,but 4 pc's for the house would be a little too expensive for me right now. What I was... (4 Replies)
Discussion started by: bilal_aa
4 Replies
10. UNIX for Dummies Questions & Answers
Hi ,
My Sun Machine Rebooted by itself 2 days back . Its running fine now , But i wanted to find out wat caused it to reboot...
This is wat the var/adm/messages show .
Kern.notice:- System booting after fatal error FATAL...
Wat causes this message ...
And wat tasks should i do to ensure it... (6 Replies)
Discussion started by: DPAI
6 Replies
tsalarm(7D) Devices tsalarm(7D)
NAME
tsalarm - Alarm device driver
SYNOPSIS
tsalarm@0:ctl
DESCRIPTION
The tsalarm driver is a Multi-threaded, loadable non-STREAMS pseudo driver that manages ALOM alarms. The tsalarm driver provides an inter-
face through which alarm relays can be controlled on SUNW,Netra-240 and SUNW,Netra-440 platforms.
HARDWARE INTERFACE
The alarm hardware differs depending on platform. The Netra 240 and 440 platforms features four dry contact alarm relays which are
controlled by ALOM. You can set each alarm to "on" or "off" by using ioctl interfaces provided from the host. The four alarms are labeled
as "critical," "major," "minor," and "user." The user alarm is set by a user application depending on system condition. LED's in front of
the box provide a visual indication of the four alarms. The number of alarms and their meanings/labels may vary across platforms.
IOCTLS
The interface provided by the tsalarm driver comprises ioctls that enable applications to manipulate the alarm module. The alarm module is
accessed via two device nodes: i) /dev/lom and /dev/tsalarm:ctl.
The following ioctls are supported by the /dev/lom and /dev/tsalarm:ctl devices:
TSIOCALCTL - Turn an alarm on or off.
The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer
which specifies the alarm to which the command is to be applied. The alarm_state/state structure member indicates the state to which
the alarm should be set (where 0 == off). An error (EINVAL) is returned if either an invalid alarm_no or invalid alarm_state is pro-
vided.
TSIOCALSTATE - Get the state of the alarms.
The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer
which indicates the alarm to which the command will be applied. The alarm_state member holds the alarm's current state and is filled
in by the driver. A zero indicates that the alarm is off. An error (EINVAL) is returned if an invalid alarm_no is provided. The struc-
tures and definitions for the values are defined below.
Alarm values:
The following old style values are defined in <lom.io.h>
#define ALARM_NUM_0 0 /* number of zero'th alarm */
#define ALARM_NUM_1 1 /* number of first alarm */
#define ALARM_NUM_2 2 /* number of second alarm */
#define ALARM_NUM_3 3 /* number of third alarm */
Alarm values defined in <lom.io.h>
#define ALARM_OFF 0 /* Turn off alarm */
#define ALARM_ON 1 /* Turn on alarm */
Alarm Data Structure:
This structure is defined in <lom.io.h>
typedef struct {
int alarm_no; /* alarm to apply command to */
int alarm_state; /* state of alarm (0 == off) */
} ts_aldata_t;
Use the following LOM interfaces to get and set the alarms. These definitions are included in <lom_io.h>
#define ALARM_CRITICAL 0 /* number of critical alarm */
#define ALARM_MAJOR 1 /* number of major alarm */
#define ALARM_MINOR 2 /* number of minor alarm */
#define ALARM_USER 3 /* number of user alarm */
The following alarm data structure is provided in <lom_io.h>:
typedef struct {
int alarm_no;
int state;
} lom_aldata_t;
ERRORS
An open() will fail if:
ENXIO The driver is not installed in the system.
An ioctl() will fail if:
EFAULT There was a hardware failure during the specified operation.
EINVAL The alarm number specified is not valid or an invalid value was supplied.
ENXIO The driver is not installed in the system or the monitor callback routine could not be scheduled.
EXAMPLES
How to set an alarm:
#include <sys/unistd.h>
#include <fcntl.h>
#include <stdio.h>
#include <lom_io.h>
#define LOM_DEVICE "/dev/lom"
int
main()
{
lom_aldata_t lld;
int fd = open(LOM_DEVICE, O_RDWR);
if (fd == -1) {
printf("Error opening device: %s0, LOM_DEVICE);
exit(1);
}
lld.alarm_no = ALARM_CRITICAL; /* Set the critical alarm */
lld.state = ALARM_ON; /* Set the alarm */
if (ioctl(fd, LOMIOCALCTL, (char *)&lld) != 0)
printf("Setting alarm failed");
else
printf("Alarm set successfully");
close(fd);
}
FILES
/dev/lom
LOM device.
/dev/tsalarm:ctl
Alarm control device.
/platform/platform/kernel/drv/sparcv9/tsalarm
Device driver module.
/platform/SUNW,Netra-240/kernel/drv/tsalarm.conf
Driver configuration file.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcarx.u |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5)
Writing Device Drivers
SunOS 5.11 16 Mar 2004 tsalarm(7D)