I'm trying to list all open sockets and their PIDs on Solaris 10 in C++.
In Solaris 11, they made this really simple by adding the PID to the mib structs (example, tcpConnCreationProcess in inet/mib2.h). This functionality isn't in Solaris 10, and can be seen in the new netstat source code.
In Solaris 10, I'm trying to use the KVM interface to get this information. Now I have the exact opposite problem where I can get the PIDs and fds without a problem, but getting the actual socket seems to be difficult.
According to some reading, the vnode struct contains the socket object (sonode?).
Is there an easy way to go from where I am to getting the socket information?
Hello,
I actually try to make client-server program.
I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error :
I'm just using this simple code :
and I get the same error if I use :
If someone can help me,
Thanks (2 Replies)
I have been serching for a guide to unix C network programming everywhere but I have found only some tuorials, very useful but a little bit poors.
My question is if exist a network domain all over the world where C socket is treated with examples.
Programs i have looked into is hard to... (4 Replies)
Please need to setup a IP Socket on SCO Open Server 5.06 / 5.07 to a Linux machine.
Al that I want to do is via a simple shell command open a tcpip address, port number, and send a call to a progam with a name of a file on the linux box.
My programming language does not support socket... (1 Reply)
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Hi all,
On the server side, one socket is used for listening, the others are used for communicating with the client.
My question is: if i want to set option for socket, which socket should be set on?
If either can be set, what's the different?
Again, what's the different if set option... (1 Reply)
Hey, I'm new to the bsd kernel and i'm implementing a vop_read function. The problem I'm having is determining
1. Which physical block is being read given the vnode's logical block #
2. How many bytes are being read
Any tips are greatly appreciated! (0 Replies)
Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct...
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <string.h>
#include... (3 Replies)
Dear Experts,
i am compiling my code in suse 4.1 which is compiling fine,
but at runtime it is showing me for socket programming error no 88
as i searched in errno.h it is telling me socket operation on non socket,
what is the meaning of this , how to deal with this error , please... (1 Reply)
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
LEARN ABOUT NETBSD
kvm_read
KVM_READ(3) BSD Library Functions Manual KVM_READ(3)NAME
kvm_read, kvm_write -- read or write kernel virtual memory
LIBRARY
Kernel Data Access Library (libkvm, -lkvm)
SYNOPSIS
#include <kvm.h>
ssize_t
kvm_read(kvm_t *kd, u_long addr, void *buf, size_t nbytes);
ssize_t
kvm_write(kvm_t *kd, u_long addr, const void *buf, size_t nbytes);
DESCRIPTION
The kvm_read() and kvm_write() functions are used to read and write kernel virtual memory (or a crash dump file). See kvm_open(3) or
kvm_openfiles(3) for information regarding opening kernel virtual memory and crash dumps.
The kvm_read() function transfers nbytes bytes of data from the kernel space address addr to buf. Conversely, kvm_write() transfers data
from buf to addr. Unlike their SunOS counterparts, these functions cannot be used to read or write process address spaces.
RETURN VALUES
Upon success, the number of bytes actually transferred is returned. Otherwise, -1 is returned.
SEE ALSO kvm(3), kvm_close(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3), kvm_getprocs(3), kvm_nlist(3), kvm_open(3), kvm_openfiles(3)BSD June 4, 1993 BSD