02-05-2007
help me stop spammer
Hello,
I am hosting a site that someone is bouncing a huge amount of spam off of and I have not been able to find what file they are using to abuse my server.
Short of terminating the account and telling my customer to take a hike I am hoping someone can help me find the file that is being used to bounce these emails out of.
Server is running apache 2, exim email, php4.4.4 and the site in question is a very plain site with a few simple javascript files and a contact form.
Any help will be appreciated and I will happily provide any further information that might assist you in helping me put a stop to this.
Regards
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Am having trouble trying to stop the process below ...
bash# ps -eaf | grep "tape erase"
root 29715 1 0 05:16:22 ttyp1 00:00:00 tape erase /dev/rStp0
root 22464 20933 1 03:40:12 ttyp6 00:00:00 grep tape eraseI've tried ... `kill -9 29715` ... but still no luck.
Help... (8 Replies)
Discussion started by: Cameron
8 Replies
2. Solaris
Hi,
I have a sun sparc system. I don't have a sun keyboard, hence i connected a pc keyboard.
I would like to know the "STOP A" equivalent command to be used on pc keyboard.
Regards,
Raja (4 Replies)
Discussion started by: RajaRC
4 Replies
3. SCO
i hit ping to ping a server, and it keeps going.
how do you stop it? ctrl Z, D, C, nothing works. (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
4. UNIX for Advanced & Expert Users
Hi ,
I have one question, suppose i am a normal user and when i use 'w' command , it shows who is logged on and what they are doing .
Now i want to stop others users to know what i am doing accept the root ?
can i do this ?
thanks (5 Replies)
Discussion started by: mobile01
5 Replies
5. AIX
Dears all
i have an AIX box in which i am facing a problem with a process as below:
/usr/dt/bin/dtexec -open 0 -ttprocid
and each time i am killing this process with "kill -9" then it run again after a while.
any ideas or solutions will be appreciated. (13 Replies)
Discussion started by: TheEngineer
13 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I am running parallel process as they all run the same JOBS and only thing which changes is the argument which ia passed.
I am doing it as follows
script.sh $1 &
script.sh $2 &
script.sh $3 &..
and so on.
Now each process has same set of JOBS which are to be executed. Now say... (1 Reply)
Discussion started by: Prashantckc
1 Replies
7. Solaris
I am using solaris x86 with a pc keyboard. i am trying to get to the ok prompt i have tried ctrl-break but it is not working , alt-break will not as well.
pls any thought? (4 Replies)
Discussion started by: seyiisq
4 Replies
8. Solaris
Hello all. I have a Solaris 10 box and I want to install a later version of Apache than what ships with the OS.
Before I install the later version, I want to completely stop the current version of Apache (the httpd service) from running or from starting at boot time.
What is the best way to... (3 Replies)
Discussion started by: RobertSubnet
3 Replies
9. UNIX for Dummies Questions & Answers
I have the following log file running since yesterday and its consuming so much of the disk space.
-rw-rw-r-- 1 dev dba 4543237120 Nov 10 09:00 load_run_file1_0.1111091224.lg
How do i kill this process. I don't have any idea of stopping this. Any help would be really appreciated.
... (3 Replies)
Discussion started by: bobby1015
3 Replies
10. Red Hat
I have a user ( and actually me too) getting this messages when the screen is idle, I need help on stopping this messages:
2012 Feb 20 13:30:22 servername Audit: LENGTH: "330" SESSIONID: "339384" ENTRYID: "1" STATEMENT: "1" USERID: "OPS$PT2ADM" USERHOST: "zzzzzzzzzzz" ACTION: "100" RETURNCODE:... (2 Replies)
Discussion started by: 300zxmuro
2 Replies
LEARN ABOUT OSF1
rpc.lockd
rpc.lockd(8) System Manager's Manual rpc.lockd(8)
NAME
rpc.lockd, lockd - Network lock daemon
SYNOPSIS
/usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]
OPTIONS
The default behavior will create and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
socket per protocol will be created and bind to the passed IP address. Available only on TruCluster Server systems. This option starts the
clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly. Highly available NFS service is config-
ured by default and typically does not require intervention. If you do need to start the clusterwide lock daemon, use the CAA command,
caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual. Internal Use Only. Use this option only under the direction
of technical support personnel. Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period dura-
tion instead of the default value of 15 seconds. Internal Use Only. Causes the rpc.lockd daemon to use the variable timeout (in
seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.
DESCRIPTION
The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status monitor daemon, rpc.statd,
for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests. Client site lock daemons
are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests. If a client site's lock daemon
fails to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
locks and cannot reclaim them.
SEE ALSO
Commands: rpc.statd(8)
Functions: fcntl(2), signal(2), lockf(3)
rpc.lockd(8)