Dear Anthony:
Thanks for your comment. I regularly peruse this and the newbie list and am always open to constructive information.

When we read information written by others describing a problem, sometimes the problem is described exactly as it is; sometimes there is more behind the description which has not been conveyed sufficiently well.

I have learned to not assume one particular scenario or view based upon what is described so I ask questions which help me understand the situation better.

My initial response expressed a concern that his system/network was compromised such that it was told to induce the sleep mode. If this was all his system was induced to do, that would be great but we know that much worse could have been done and is possible to do, which is why I addressed his question utilizing a Systems or Wholistic style approach. His question remember, included the phrase, "how to completely disable anything ..."; I introduced Tripwire into the discussion for his consideration so that he could discover whatever attack was going on by using it. Tripwire is very powerful tool for tracking what is being attacked, how and even in what manner ... it tracks everything and keeps logs of whatever is going on and can negate any process from proceeding forward was well. Tripwire is perfect for discovering the fact and existence of an actual attack if one is in fact occurring. However, if one does not have Tripwire it is extremely difficult to determine the source and manner of how an attack was executed. Tripwire after it has learned the normal operations of a system can stop absolutely nearly anything thrown at it, and so it is an appropriate tool for him which could effectively stop any outside program which may induce or may have induced that behavior or any other unauthorized system behavior. And if his authorization is merely that of a user, he can possibly pass on the information shared to his System Administrator for possible implementation of the commercial or open source version of Tripwire where appropriate and necessary.

In the process of a later exchange I brought out the point of other possible solutions which could be done from within a control panel or other system option which may also have been overlooked.

Usually when someone writes that they want to disable "anything" they usually mean that they intend to disable anything that causes the behavior or action that they are complaining about, AND any other thing imitating or proceeding or causing other unknown or unexpected effects within a system. It turns out that everything is a matter of interpretation -- English, just as any human language is not precise as a mathematical equation or even as precise as a score of Beethoven or Mozart or other musical script.

There is room to interpret and view many things, many ways especially over time. Remaining flexible to such is an Art; all anyone can do is work to refine oneself in it.

On Nov 9, 2005, at 11:05 PM, Anthony Lanni wrote:

Jonathan, check your APM or ACPI settings.  You can quickly check which one you're using by looking in /proc; one or the other (usually not both) will be there.  Both are easily googled, as well. My yellowdog box defaulted to APM; that's not really a problem, since it's a laptop anyway, but I
 suggest upgrading to ACPI for support and configurability.

Also check the Advanced tab in the Screensaver control panel.  You may be able to ignore my
 previous paragraph completely.

And Derick, if I may offer a bit of advice; please read people's questions more carefully in order to provide a useful solution set.  The original post - which you thoughtfully included in your first reply - makes it clear that the machine just went to sleep, not just once but twice.

On 10/5/05, Derick Centeno <[EMAIL PROTECTED]> wrote:
...  From your more detailed
description this time around it appears that your system didn't
shutdown; it was merely asleep.  Completely different scenario than
what was described. ...
  
On Oct 5, 2005, at 2:05 PM, [EMAIL PROTECTED] wrote:

 > Hello,
 >
 > I'm trying to set up YDL 4.0.1 as a server and this morning when I
> came back to work, I found that the OS was asleep - I couldn't ping or connect
 > to any services.
 >
> Does anyone know how to completely disable anything that would put the
 > computer to sleep?
 ...



--
"The Code of the Knighthood is not idle suggestion; it is law
for all those who wear the sign of the Blade, Rose and Tome.
A Knight is Honest; Loyal; Helpful; Friendly; Courteous; Kindly;
Obedient; Cheerful; Thrifty; Brave; Clean; and Respectful.
Heed the 12 Laws in every word and deed."
                                             -Faentur, Knights Humanitas_______________________________________________
yellowdog-general mailing list
[email protected]
http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'


================================
Life only demands from you the strength that you possess. Only one feat is possible; not to run away.
-- Dag Hammarskjold (July 29, 1905 - September 18, 1961)
_______________________________________________
yellowdog-general mailing list
[email protected]
http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'

Reply via email to