02-06-2008
Yep, as I suspected, that's not at all a Solaris O/S.
This thread should be moved to the SCO forum.
10 More Discussions You Might Find Interesting
1. BSD
# cd /usr/src/sys/i386/conf
# cp GENERIC LOVEPP
# cd /usr/src
# make buildkernel KERNCONF=LOVEPP
make:don't know how to make buildkernel. Stop
Any suggestions?
(I am using Freebsd4.8) (2 Replies)
Discussion started by: sheep
2 Replies
2. UNIX for Advanced & Expert Users
Hi All
I am kinda wondering about the UX kernel parameters, how we configure and why do we configure ???.. especially the 'semaphores'. Could somebody throw some light on this and would really appreciate it. (1 Reply)
Discussion started by: Prince_Charming
1 Replies
3. Solaris
When I run the Oracle installer, following checks are failed:
Checking for shmsys:shminfo_shmmax=4294967295; found no entry. Failed <<<<
Checking for shmsys:shminfo_shmmni=100; found no entry. Failed <<<<
Checking for semsys:seminfo_semmni=100; found no entry. Failed <<<<
Checking... (1 Reply)
Discussion started by: aa_monster
1 Replies
4. UNIX for Dummies Questions & Answers
I'm getting the following Error:
prepare_pcap.c: In function `prepare_pkts':
prepare_pcap.c:127: error: dereferencing pointer to incomplete type
prepare_pcap.c:138: error: dereferencing pointer to incomplete type
====================================
This is the part of the relevant... (8 Replies)
Discussion started by: katwala
8 Replies
5. Solaris
I tried to install the kernel patch 118855-36 in my x86 machine which has Solaris 10 installed. Find below the error message....
#patchadd 118855-36
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
118855-36
Executing... (1 Reply)
Discussion started by: paventhan
1 Replies
6. UNIX Benchmarks
Just for fun:
CPU/Speed: 2x AMD Opteron Model 2384 (2.7GHz/512KB) quad core processor
Ram: 4 x2GB ECC DDR2-667 single rank memory
in RAID 0 mode (strip 128KB, Read Caching enabled, Write Caching disabled) with 2 HDD, CPUTYPE=opteron, CFLAGS= -O2 -fno-strict-aliasing -pipe, CXXFLAGS+=... (0 Replies)
Discussion started by: Success_Tree
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies
8. Linux
Hi,
Can i just ask how I can create a bootable PXE image from the built kernel source.
What files do I need to get?
Thanks! (1 Reply)
Discussion started by: h0ujun
1 Replies
9. Solaris
Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error.
Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies
10. SuSE
http://uploads.tapatalk-cdn.com/20160725/0174562490859032f68430fb0fa216cd.jpg
I have created a personally made SUSE-based distro using susestudio.com and it will install just fine on my laptops (32-bit Acer Aspire One ZG5 and MacBook 4,1). However, when installing on an old Emachine desktop, I... (6 Replies)
Discussion started by: TheOuterLinux
6 Replies
niff(7) Miscellaneous Information Manual niff(7)
NAME
niff - Network Interface Failure Finder (NIFF) introductory information.
DESCRIPTION
The Network Interface Failure Finder, NIFF, is a facility for detecting and reporting possible failures in network interface cards (NICs)
or their connections. Detection is done by monitoring device counters and attempting to generate traffic to NICs suspected of having
failed. Reporting is done using the Event Manager subsystem (EVM). NIFF does not drive failover operations; that is the responsibility of
the application that subscribes to NIFF's EVM events. Appropriate courses of action may include selecting another network interface for
communication or if it is a clustered environment, migrating an application. See nr(7) for further information.
At the heart of NIFF is the traffic monitor thread. The traffic monitor thread tracks changes in the network device's counters, and notes
if the received packet counter remains unchanged since the previous snapshot. As long as the counter continues to increase, the traffic
monitor thread assumes the NIC is functioning. See nifftmt(7) for further information.
The traffic monitor thread can monitor any network interface. The configuration utility, niffconfig, is used to activate and administer
the traffic monitor thread. See nifftmt(7) and niffconfig(8) for further information.
The Network Interface Failure Finder daemon, niffd, is a traffic generator for network interfaces that have been classified inactive by the
kernel traffic monitor thread. The purpose of niffd is to get the interface packet counters to increment, signifying the interface is still
alive and well. See niffd(8) for further information.
SEE ALSO
:
nifftmt(7), nr(7), niffconfig(8), niffd(8) delim off
niff(7)