10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
2. Programming
Hi
I try to communicate with a GSM modem, from C, for sending SMS.
I use standart AT-commands.
Working well with terminal.
There is no problem writing ti the port.
But when I try to read I only get a echo, I write "ATI" and get "ATI" back, I should get somthing like "SIEMENS 35... (4 Replies)
Discussion started by: dmiller
4 Replies
3. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
4. UNIX for Dummies Questions & Answers
A neighbour's Ubuntu 10.04 machine has five serial ports, one on the motherboard and four on a PCI card. However, only four cards are showing:
# dmesg | grep tty
console enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
... (2 Replies)
Discussion started by: dotancohen
2 Replies
5. Solaris
What is the serial port on the T5140 used for. (4 Replies)
Discussion started by: pgsanders
4 Replies
6. AIX
Hi,
How can i configure my modem in AIX thru serial port (sa0-->tty0)
I have two port serial card configured as sa0
I created tty1 which port is tty0 and which port is tty1 how can i know?? (1 Reply)
Discussion started by: pchangba
1 Replies
7. Programming
I am developing an application in c with Linux OS, where a radio modem working at baud rate 9600 will be attached to PC on serial port. More than four such units will be communicating at one time, so there may be jamming or data corruption. Each module will be transmitting Data packets less than... (2 Replies)
Discussion started by: raj8109
2 Replies
8. UNIX for Advanced & Expert Users
I am using system running on red hat linux 4.
I had connected health measuring machine to the serial port and configured it
stty -F /dev/ttyS0 9600 -parenb cs8 -cstopb
this machine requires a command to be passed to it for giving output. I am unable to pass command hexa format(0x68) to the... (4 Replies)
Discussion started by: netsavant
4 Replies
9. Solaris
Hi,
I'm using Solaris workstation with 5.4 OS.
I was wondering if there's a way that I could
log the data incoming and outgoing on a certain
serial port.
Thanks in Advance! (1 Reply)
Discussion started by: uryuu
1 Replies
10. Programming
I'm writing a journal_write() function and I want it to:
- be a possible drop in replacement for write()
- write entries to the journal ;-) Could be a regular file (journal.txt), a serial printer or a // printer.
- handle printer status if needed.
fstat() tells weather or not we're dealing with... (2 Replies)
Discussion started by: starless
2 Replies
POWERD(8) System Manager's Manual POWERD(8)
NAME
powerd - UPS monitoring daemon
SYNOPSIS
/sbin/powerd [tty]
DESCRIPTION
powerd monitors the serial port connected to an UPS device and will perform an unattended shutdown of the system if the UPS is on battery
longer than a specified number of minutes. powerd needs to watch a tty with modem control properties. Please refer to the powerd documen-
tation for further information.
powerd also has the capabilities of notifying other clients on the network that may have a UPS but not be connected to the serial line that
there is a power outage, and id configured through the powerd.conf file
CONFIGURATION FILE
Here is the configuration format:
Lines beginning with '#' are ignored.
MODE <mode>
specifies the mode the UPS should be in. Valid arguements are MONITOR and PEER MONITOR being the mode to actually watch a UPS serial
port, and PEER being to listen for a connection from a machine in MONITOR mode
MONITOR <device>
Specifies which device to monitor while in MONITOR mode. Specify an actual device file. Example: /dev/ttyS0
POWERFAIL <line> <high|low>
Specifies which lines on the serial ports indicate that the power is out. Valid arguements are DCD, CAR, CTS, and RNG. Also specify
if the line being HIGH or LOW indicates a power failure.
Since most people may not know this arguement, Please use the enclosed upsdetect program to automatically find this line.
NOTIFY <hostname[:port]> <password>
Specified in MONITOR mode to notify a client running in PEER mode. Specify the hostname of the machine, and optional port the daemon
is running on, And the password as specified by their LISTEN command. See below for more details.
LISTEN <hostname> <password>
Specified in PEER mode, specifies a hostname that is allowed to notify us of when the power is out, and the password they shall give
us to authenticate themselves. The 2 passwords should match on the MONITOR mode machines NOTIFY password, and the PEER modes LISTEN
password.
LISTENPORT <port>
Specified in PEER mode, specifies the port that powerd should listen on. If you use this arguement, powerd shall not default to
using port 532, and the machine in MONITOR mode must specify the port you use in their NOTIFY command.
DELAY <delayinseconds>
Specifies how many seconds before notifying init of a power outage. Note that this doesnt mean that the system will shut down in
that many seconds, as it depends on how init is configured. Init usually issues a 2 min shutdown.
USER <username>
Specifies which username to drop to from root. The program will reobtain root access only when it needs to, Like when notifying init
that the power is out. This is simply a security feature, and not needed for powerd to operate. Note: powerd must still be run ini-
tially as root. It will then drop to the user if, and only if, a username is specified.
ARGUMENTS
None: Please use the configuration file /etc/powerd.conf which can be generated with detectups. See detectups(8) for more information
FILES
/etc/powerd.conf powerd configuration file
/etc/powerstatus indicates line power status
/etc/inittab init is what actually issues the shutdown
SEE ALSO
powerd(8), shutdown(8), wall(1), init(8), inittab(5).
AUTHOR
James Brents <James@nistix.com> (with parts of this man page borrowed from all over the Linux community)
POWERD(8)