InsomniaT failing to prevent sleep

[wfaulk]

I find that my MacBookPro is frequently going to sleep while InsomniaT is active. Unlike before, where VNC activated sleep for some reason, this seems to happen randomly. It also doesn't seem to go to sleep immediately after I close the lid, but some random time later. Unfortunately, I don't have any further idea about what could be causing it to go to sleep. Are there any logs that would indicate the reason it goes to sleep? Or any way to get InsomniaT to record all of the sleep requests it sees? As an enhancement, maybe it could allow the user to select which sleep requests are honored and which aren't.

[Archimedes Trajano (trajano)]

I took out the logs, the only time it does the sleep is when it detects the lid is closed. Unless VNC is sending the message that the lid is closed then it shouldn't.

How random a time are you talking about when you say a random time later? I find that on high CPU load it takes an extra few seconds for it to go on sleep mode.

Not sure what VNC does to do it. Are we talking about the stock VNC screen sharing that comes with MacOS?

[wfaulk (wfaulk)]

What I mean is that I have InsomniaT enabled (sleep disabled) and I close the lid. Most, if not all, of the time, it seems to stay awake. But then I'll come back hours later and it's in sleep. I don't know when it happens. I suppose it's possible that it's just taking an awfully long time to go to sleep initially.

I'm using the Vine VNC server. There was something (that I can't remember now) that made the stock VNC server unusable for me.

My point about the logs is: surely there are other events that initiate sleep, like low battery. And you're able to detect that the lid being closed is not one of those events. Assuming that InsomniaT isn't broken, and that a different sleep request is being made, can't InsomniaT record a log of all sleep requests that it sees? Or is it somehow binding to only listen for the one type of sleep request?

And if I could get that information, I could determine what's causing the laptop to go to sleep when I'm not expecting it to.

And if it turns out that it is something else, it would be nice if I could tell InsomniaT to ignore those requests, too.

[Archimedes Trajano (trajano)]

What I can do is add a new parameter to enable logging, default will still be disabled. I'll try to target it by end of next week. The reason logging was disabled was there was no way of being "selective" on what goes to the system logs so rather than pollute it, I just got rid of logging entirely.

I'll need you to tell me what would be triggering your problem because I am not sure how to replicate it myself.

[Archimedes Trajano (trajano)]

I added logging capability to the new release of insomniat. Please check if you are still having trouble. If so open up a new bug and paste the output of kernel.log if you see anything unusual.