You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for suspending my non-systemd distro. The problem here is not of an needed -s suspend command upgrade, but rather to make something like betterlockscreen -l -e, with the -e option being like a wait option until betterlockscreen is actually loaded, and then it passing away as a background process, letting the shell do its thing.
The problem with this is that without the sleep command the system would go sleep, and then when its woken up there will be a slight time of the system not being locked, and then locking itself, due to betterlockscreen not being fast enough. If instead i just removed the & at the end of the command, the system would wait for blscreen to unlock and only then will it suspend the machine.
However what if my system, for some reason, such as a nearly full ram, is slow, and betterlockscreen doesnt get to lock it in the right time (0.5 secs)?
Can an option such as -e, to let betterlockscreen hand only for the amount of time that it is not active, be brought?
The text was updated successfully, but these errors were encountered:
Yeah, the scripts just tried to call systemctl, doesnt work. Although i dont think i will do something like patch my system to execute betterlockscreen everytime it goes into suspending, maybe sometime i want to suspend it without locking it. Until something better of a solution comes, i guess i could just go on like this or edit the command in betterlockscreen.
In my scripts, i use:
for suspending my non-systemd distro. The problem here is not of an needed -s suspend command upgrade, but rather to make something like betterlockscreen -l -e, with the -e option being like a wait option until betterlockscreen is actually loaded, and then it passing away as a background process, letting the shell do its thing.
The problem with this is that without the sleep command the system would go sleep, and then when its woken up there will be a slight time of the system not being locked, and then locking itself, due to betterlockscreen not being fast enough. If instead i just removed the
&
at the end of the command, the system would wait for blscreen to unlock and only then will it suspend the machine.However what if my system, for some reason, such as a nearly full ram, is slow, and betterlockscreen doesnt get to lock it in the right time (0.5 secs)?
Can an option such as -e, to let betterlockscreen hand only for the amount of time that it is not active, be brought?
The text was updated successfully, but these errors were encountered: