04-10-2001
sorry...
sorry I keep replying to my own posts heh but I found out the problem. if you have a HP A Class server don't set the lan console ip and the machine ip on lan0 the same, or else this produces a conflict in STREAMS/UX whereby collisions occur. the t_error_ack means that an acknowledgement cannot be recieved from some software (sw in this case) due to collisions.
hope this saves someone some grief in the future!
thanks
Regards
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
What are transparent ioctls messages and when and why we have to issue copyin or copyout kernel utilities with respect to ioctls calls to a Stream. (2 Replies)
Discussion started by: S.P.Prasad
2 Replies
2. SCO
Anybody have a clue what might have caused the Failures under Class 6? I did a reboot and so far so good, I had been up for about 55 days prior to the reboot. I'm running SCO_SV rel 3.2v5.0.7.
Steve
#netstat -m
streams... (1 Reply)
Discussion started by: Steve_93630
1 Replies
3. Programming
#include "../ourhdr.h"
int main(void)
{
int c;
char *buf;
setvbuf(stdin,buf,_IONBF,10);
setvbuf(stdout,buf,_IONBF,10);
while((c=getc(stdin)) != EOF)
{
if(putc(c,stdout) == EOF)
err_sys("output... (2 Replies)
Discussion started by: gandhevinod
2 Replies
4. Shell Programming and Scripting
Here is an example code that shows the issue I have:
#!/bin/bash
counter() {
seq 1000 | while read NUM; do
echo $NUM
echo "debug: $NUM" >&2
sleep 0.1 # slow it down so we know when this loop really ends
done
}
counter | grep --line-buffered "" | head -n1
... (10 Replies)
Discussion started by: tokland
10 Replies
5. AIX
Hi all,
I have a AIX kernel STREAMS question need your help,
I need to implement a firewall on AIX and get packet raw data then decide pass or drop it,
I've seen similiar firewall code on HP-UX,
on HP-UX, you have to implement a "dlpi STREAMS driver", and specify it as a "dlpi" driver in... (1 Reply)
Discussion started by: rocktilldie
1 Replies
6. Programming
Hi,
Mentioned in Stevens & Rago "Advanced Programming in the UNIX"
I don't understand why must flush all line-buffered output streams when (a)an unbuffered or (b)a line-buffered stream require data from kernel? (2 Replies)
Discussion started by: Edward114
2 Replies
7. Shell Programming and Scripting
hallow all i need your advice about this script
i have script like this:
INDEX=/zpool1/NFS/INDEX/${1}
SCRIPT=/zpool1/NFS/script/${1}
LIST=SAMPLE
cd ${SCRIPT}
for i in `cat ${LIST}`
do
GETDATE=`echo ${i}|awk '{print substr($1,9,8)}'`
/usr/xpg4/bin/awk -F ":" '{close(f);f=$4}{print >>... (4 Replies)
Discussion started by: zvtral
4 Replies
STREAMS(4) BSD/i386 Kernel Interfaces Manual STREAMS(4)
NAME
streams -- System V STREAMS networking ABI support
SYNOPSIS
To compile support for this ABI into the kernel, place the following line in your kernel configuration file:
device streams
Alternatively, to load the ABI as a module at boot time, place the following line in loader.conf(5):
streams_load="YES"
DESCRIPTION
The streams module provides limited System V Release 4 STREAMS interprocess communication ABI (application binary interface) compatibility
for userland applications.
Internally, streams provides STREAMS handles by using socket creation kernel routines, and adding state-tracking information to the socket to
permit manipulation by STREAMS emulation code in svr4(4). Hence, opening a stream device produces a result similar to what would be obtained
by calling socket(2).
Applications should never use this interface directly: STREAMS emulation is only provided as a service to support ABI requirements in the
SVR4 environment which svr4(4) needs to present to client binaries.
SEE ALSO
svr4(4)
HISTORY
System V Release 4 ABI support first appeared in FreeBSD 4.0. The ABI was ported from an equivalent facility present in NetBSD 1.3 written
by Christos Zoulas.
BUGS
This whole interface is a crude hack to produce STREAMS semantics through emulation over sockets.
Programmers who hope to be able to use this interface to provide SVR4 STREAMS services to BSD applications will be sorely disappointed.
BSD
March 17, 2008 BSD