Can you set up a second listener in /devices/pseudo? What about using a different minor number?
I am trying to get Domino to listen from 2 different local zones. They are each running different versions of Domino. Any help would be appreciate.
Here is some more info:
The first zone worked fine. It was running Domino8 - no problems.
The new zone is completely different: it is a Solaris 8 zone (whole zone) running an old version of Domino (6 or 7 I'm not sure). It is also using Oracle9ais, and j2ee (there is a conflict that shows up with ORMI. I did not install this version of Domino in the global, however, I believe it may be old enough that it would not be required.
I just added a new ethernet port to the mix in case that helps. But when i check the major and minor numbers by doing and ls -l on /devices/pseudo/listen* I only get one line and I'm afraid that is causing the conflict when I add that same listener to both zones.
hello
can help to script to find the listener is up or down for diferent db
i have 2 listener
ps -fea |grep tns
root 17333 17559 0 12:26:38 pts/3 0:00 grep tns
oracle 3800 1 1 Jul 23 ? 400:42 /u01/app/oracle/product/9.2.0/bin/tnslsnr LISTENER -inherit
... (1 Reply)
Hi Pros,
I'm writing a script to modify listener.ora file on multiple hosts. When I ssh to any server from a central server in our environment we are presented with menu to select the instance. I need to set my environment to listener which could be different number on every instance. How can I... (5 Replies)
Hi All,
I'm installation a server
we have client -server architecture
I need to configure a port for client to communicate with the server
and server to communicate with the clients
Pls let me know how to configure in linux (2 Replies)
Listener thread is maintained at server side :
I have Implemented as:
/* specify queue */
listen(sockfd, 5);
while (1) {
clilen = sizeof(cli_addr);
newsockfd = accept(sockfd,
(struct sockaddr *) &cli_addr, &clilen);
if... (0 Replies)
Hi,
I having trouble while installing domino.doc 3.5 on aix 4.3. The error details are as follows. Pls let me where i am doing wrong. Domino server6.0.2 is already installed.
# cd /ddoc/dd31aix/install
# ./install
Can't load '/usr/opt/perl5/lib/5.00503/aix/DDInst.so' for module DDInst:... (0 Replies)
Hi,
Anyone have any pointers on how I would go about creating some sort of listener (preferably, but not exclusively in Java) that would monitor an ftp port and react to arrival of a new file?
Thanks in advance.
Selma (2 Replies)
listen(1M) System Administration Commands listen(1M)NAME
listen - network listener daemon
SYNOPSIS
/usr/lib/saf/listen [-m devstem] net_spec
DESCRIPTION
The listen process ``listens'' to a network for service requests, accepts requests when they arrive, and invokes servers in response to
those service requests. The network listener process may be used with any connection-oriented network (more precisely, with any connection-
oriented transport provider) that conforms to the Transport Layer Interface (TLI) Specification.
The listener internally generates a pathname for the minor device for each connection; it is this pathname that is used in the utmpx entry
for a service, if one is created. By default, this pathname is the concatenation of the prefix /dev/netspec with the decimal representation
of the minor device number. In either case, the representation of the minor device number will be at least two digits (for example, 05 or
27), or longer when it is necessary to accommodate minor device numbers larger than 99.
SERVER INVOCATION
When a connection indication is received, the listener creates a new transport endpoint and accepts the connection on that endpoint. Before
giving the file descriptor for this new connection to the server, any designated STREAMS modules are pushed and the configuration script is
executed, (if one exists). This file descriptor is appropriate for use with either TLI (see t_sync(3NSL) ) or the sockets interface
library.
By default, a new instance of the server is invoked for each connection. When the server is invoked, file descriptor 0 refers to the trans-
port endpoint, and is open for reading and writing. File descriptors 1 and 2 are copies of file descriptor 0; no other file descriptors are
open. The service is invoked with the user and group IDs of the user name under which the service was registered with the listener, and
with the current directory set to the HOME directory of that user.
Alternatively, a service may be registered so that the listener will pass connections to a standing server process through a FIFO or a
named STREAM, instead of invoking the server anew for each connection. In this case, the connection is passed in the form of a file
descriptor that refers to the new transport endpoint. Before the file descriptor is sent to the server, the listener interprets any config-
uration script registered for that service using doconfig(3NSL), although doconfig is invoked with both the NORUN and NOASSIGN flags. The
server receives the file descriptor for the connection in a strrecvfd structure using an I_RECVFD ioctl(2).
For more details about the listener and its administration, see nlsadmin(1M).
OPTIONS -mdevstem The listener will use devstem as the prefix for the pathname.
FILES
/etc/saf/pmtag/*
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO nlsadmin(1M), pmadm(1M), sac(1M), sacadm(1M), ioctl(2), doconfig(3NSL), nlsgetcall(3NSL), nlsprovider(3NSL), t_sync(3NSL), attributes(5),
streamio(7I)
System Administration Guide: Basic Administration
NOTES
When passing a connection to a standing server, the user and group IDs contained in the strrecvfd structure will be those for the listener
(that is, they will both be 0); the user name under which the service was registered with the listener is not reflected in these IDs.
When operating multiple instances of the listener on a single transport provider, there is a potential race condition in the binding of
addresses during initialization of the listeners, if any of their services have dynamically assigned addresses. This condition would appear
as an inability of the listener to bind a static-address service to its otherwise valid address, and would result from a dynamic-address
service having been bound to that address by a different instance of the listener.
SunOS 5.10 3 Apr 1997 listen(1M)