Logsat in Stand-alone Mode and 100% Utilization |
Post Reply ![]() |
Author | |
David Rossi ![]() Guest Group ![]() |
![]() ![]() ![]() ![]() ![]() Posted: 13 September 2004 at 4:01pm |
|
|
![]() |
|
LogSat ![]() Admin Group ![]() ![]() Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
![]() ![]() ![]() ![]() ![]() |
David,I'm sorry for missing the previous post. For some reason I was sure we had responded to that by email, but that was not the case. These hurricanes caused us to slack a bit.There should never be the need to manually kill a connection, as 60 seconds after there is no input received, SpamFilter will automatically disconnect it. The processor and memory climbing by simply using telnet to enter commands and stopping at the DATA command is also very odd, we have never seen that. In that case too SpamFilter should terminate the connection after 60 seconds. Is it possible for us to remote in the server so we can see what is happening? You can email us at support@logsat.com if you wish with the info.Please note that it is "normal" however to receive errors when using the "kill" or "end task" commands to terminate the main SpamFilter ISP process, as that caused Windows to abruptly terminate whatever the main SpamFilter thread may be doing at the moment, possibly causing the other threads to cause errors as the main thread is gone.Roberto F.
LogSat Software
|
|
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.191 seconds.