Identify process sending ldap requests to old DNS server
Hi,
I have a Solaris 10 system, which appears to be sending out LDAP queries to a server that is due to be decomissioned.
Is there a way to identify which process is sending out these queries? The problem is that the local port constantly changes, and the connections do not stay open long enough to query them using netstat or lsof.
I can see the outbound traffic in snoop:
and also in netstat:
But cant think of a way to identify what process is sending this out. I've checked resolv.conf & /etc/nsswitch.conf and the decom server is not listed anywhere.
I have no idea where the information for this decomServer is coming from, or which process is sending. Is there a way I can find this out?
I have just started learning Unix on Solaris and have been asked to learn DHCP, DNS and LDAP very quick in order to implement them and maintain.
Does anyone know how to do this or a decent book that will include all the above three which tells you how to install and maintain. All i have found so... (2 Replies)
Hi all
Is there any reason to have "hosts ldap dns" as line in /etc/nsswitch.conf ? My understanding is that ldap does not contain any host information..(?)
Best regards...Ludwig (1 Reply)
Dear guys,
I am facing the most weird problem I have ever encountered!
Ok here is the situation:
From my dns query.log file - it is generated using usual bind9 logging:
logging {
channel query.log {
file "/var/log/bind9/query.log" versions 10 size 2m;
severity debug 2;... (0 Replies)
Hi everybody,
Is it possible to have a URL link i.e. <a href=""></a>, which sends out two requests to a site?
As an example, I want want to combine these two links. The first link loads files. The second link searches these files. But I want just one link, where went a user clicks on it,... (3 Replies)
My environmnet : solaris 10 u 7 sparc
To configure DNS bind use Ldap as zone record database, I use bind 9.7.0 and sun directory 5.2
I do follow http://imil.net/docs/Configuring_DNS_zones_with_LDAP.txt
and stuck at make install
Error from bind log "database: error: unsupported database... (0 Replies)
I'd like to get some opnions on choosing DNS server:
Windows DNS vs Linux BIND comparrsion:
1) managment, easy of use
2) Security
3) features
4) peformance
5) ??
I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
hi
I am seeking to create a cgi-bin type creation that will allow users browsing the site to be able to run searches that would be a grep command or SED in the backround. I am not sure how to go about this, if you would give me a pointer or direction about what technology i could inform myself... (0 Replies)
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
LEARN ABOUT BSD
kill
KILL(2) System Calls Manual KILL(2)NAME
kill - send signal to a process
SYNOPSIS
kill(pid, sig)
int pid, sig;
DESCRIPTION
Kill sends the signal sig to a process, specified by the process number pid. Sig may be one of the signals specified in sigvec(2), or it
may be 0, in which case error checking is performed but no signal is actually sent. This can be used to check the validity of pid.
The sending and receiving processes must have the same effective user ID, otherwise this call is restricted to the super-user. A single
exception is the signal SIGCONT, which may always be sent to any descendant of the current process.
If the process number is 0, the signal is sent to all processes in the sender's process group; this is a variant of killpg(2).
If the process number is -1 and the user is the super-user, the signal is broadcast universally except to system processes and the process
sending the signal. If the process number is -1 and the user is not the super-user, the signal is broadcast universally to all processes
with the same uid as the user except the process sending the signal. No error is returned if any process could be signaled.
For compatibility with System V, if the process number is negative but not -1, the signal is sent to all processes whose process group ID
is equal to the absolute value of the process number. This is a variant of killpg(2).
Processes may send signals to themselves.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Kill will fail and no signal will be sent if any of the following occur:
[EINVAL] Sig is not a valid signal number.
[ESRCH] No process can be found corresponding to that specified by pid.
[ESRCH] The process id was given as 0 but the sending process does not have a process group.
[EPERM] The sending process is not the super-user and its effective user id does not match the effective user-id of the receiving
process. When signaling a process group, this error was returned if any members of the group could not be signaled.
SEE ALSO getpid(2), getpgrp(2), killpg(2), sigvec(2)4th Berkeley Distribution May 14, 1986 KILL(2)