11-11-2014
Quote:
Originally Posted by
derekhsu
Hi,
I am trying to implement a service on AIX based on ONCRPC protocal and I want to use a RPC library called oncrpc4j because it is a non-blocked i/o library. I found it works fine on my work machine (WIndows 7) but failed on my AIX work station. The author of oncrpc4j told me that check that rpcbind/portmap on AIX allowes updates from non privileged ports. But I just can find out how to do this, is anybody could provide help? Thank you.
What you are allowed to do is usually a matter of user rights, not of protocols. Please provide details about the user account you want to use to do what you want to do and its properties.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm new to the forum and would like to know how to check
inbound traffic on various port numbers.
I would also like to know how to open and close various ports
on a unix box running solaris 8.
Thanks in advance.
sunoracle (1 Reply)
Discussion started by: sunoracle
1 Replies
2. IP Networking
Hello,
I'm new to the forum and would like to know how to check
inbound traffic on various port numbers.
I would also like to know how to open and close various ports
on a unix box running solaris 8.
Thanks in advance.
sunoracle (2 Replies)
Discussion started by: sunoracle
2 Replies
3. Shell Programming and Scripting
Hello, i need a script (bash type maybe?..), which would check open ports on 127.0.0.1 and then compare open ports with "registered/allowed" port list and try to kill the program who uses unregistered ports. It would be great that script would be started lets say every 5 or 10 minutes.
You see i... (2 Replies)
Discussion started by: MorchiuS
2 Replies
4. Cybersecurity
Hi All,
I've been using this to verify if ports is open on a server. For example I would like to check port 5887, "telnet ip.of.server 5887" using on dos. If there's response on it then I can say it's open, if not then it's close.
Is that assumption accurate?
Thanks for any comments you... (4 Replies)
Discussion started by: itik
4 Replies
5. Solaris
Please let me know how to setup a non-root user to be able to access a privileged port (<1024) on Solaris 8. I am currently running tomcat as "tomcat" user and I get the following error during to start up:
SEVERE: Error initializing endpoint
java.net.BindException: Permission denied<null>:443 (5 Replies)
Discussion started by: pingmeback
5 Replies
6. AIX
In trying to resolve my issue, I downloaded TL 11 and trying to update to it. Why the heck does not the TL fix have the required files in it? Thats another 1.+ GB download. I am also sure that when I go to install that package it will complain about rsct not being updated.
MISSING... (1 Reply)
Discussion started by: mrmurdock
1 Replies
7. AIX
Hello,
what is the relation between portmap and nfsd and how communication between them looks like. Does the nfsclient contact with the portmap or nfsd first.
Many thanks in advance for helping me to understand this :)
BR,
p (3 Replies)
Discussion started by: pitmod
3 Replies
8. UNIX for Advanced & Expert Users
Wasn't sure how to word the title... sorry.
In HP-UX and AIX specifically you apply a set of patches, not like solaris and linux where you update what's needed individually. So, for example, when going from patch level 1.1 to 1.8 is the time to complete exponential (1.1 -> 1.2 -> 1.3.. so on)... (1 Reply)
Discussion started by: gville2otown
1 Replies
9. UNIX and Linux Applications
Can anyone explain how Firefox updated when Never Check for updates is selected? (4 Replies)
Discussion started by: cokedude
4 Replies
10. Proxy Server
On HP_UX i download the patches and then install with swinstall
On AIX,i found "service packs" but there are many,i have to install all service packs,or the latest is ok?
Thanks (5 Replies)
Discussion started by: Linusolaradm1
5 Replies
LEARN ABOUT REDHAT
rpc.statd
rpc.statd(8) System Manager's Manual rpc.statd(8)
NAME
rpc.statd - NSM status monitor
SYNOPSIS
/sbin/rpc.statd [-F] [-d] [-?] [-n name ] [-o port ] [-p port ] [-V]
DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnomed, since it doesn't actu-
ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file
locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots.
Operation
For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/statd/sm. When starting, it iterates
through these files and notifies the peer rpc.statd on those machines.
OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground.
This option is mainly for debugging purposes.
-d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr
instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter.
-n, --name name
specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname.
Specifying a local hostname may be useful for machines with more than one interfaces.
-o, --outgoing-port port
specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port
number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be
useful when implementing a firewall.
-p, --port port
specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ-
ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing
a firewall.
-? Causes rpc.statd to print out command-line help and exit.
-V Causes rpc.statd to print out version information and exit.
TCP_WRAPPERS SUPPORT
This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed
to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:
statd: .bar.com
You have to use the daemon name statd for the daemon name (even if the binary has a different name).
For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.
FILES
/var/lib/nfs/statd/sm/state
/var/lib/nfs/statd/sm/*
/var/lib/nfs/statd/sm.bak/*
SEE ALSO
rpc.nfsd(8), portmap(8)
AUTHORS
Jeff Uphoff <juphoff@transmeta.com>
Olaf Kirch <okir@monad.swb.de>
H.J. Lu <hjl@gnu.org>
Lon Hohberger <hohberger@missioncriticallinux.com>
08 Mar 2001 rpc.statd(8)