Re: [Swsusp-devel] Re: Thoughts wanted on merging Software Suspend enhancements

Vojtech Pavlik
2003-07-15T06:22:13Z

On Tue, Jul 15, 2003 at 01:02:19AM +0200, Pavel Machek wrote:

> > > > > Having listened to the arguments, I'll make pressing Escape to cancel
> > > > > the suspend a feature which defaults to being disabled and can be
> > > > > enabled via a proc entry in 2.4. I won't add code to poll for ACPI (or
> > > > > APM) events :>
> > > >
> > > > I'd suggest making it a mappable function in the keymap, like reboot is
> > > > for example. Both for initiating and stopping the suspend. How about
> > > > that?
> > >
> > > Any user can load his own keymap, I believe... And I do not like
> > > having special /proc options for esc key...
> >
> > So what? He can press ctrl-alt-del or whatever if he has access to the
> > keyboard anyway. Nevertheless I don't see any way to cause harm by
> > cancelling a sw-suspend other than if a server was shutting down due to
> > the UPS batteries being empty. And in that case the machine will be in a
> > locked room anyway.
>
> ctrl-alt-del maps to "echo you lost" on many machines. It just signals
> init, does nothing more.
>
> That UPS is bad enough... It should be okay to have server locked but
> have its keyboard/monitor publicly available.

I'm very much sure this feature (having a server locked, while
keyboard/screen is accessible) is much LESS useful than being able to
stop an suspend in progress. That's if the suspend isn't lightning fast,
of course, which is is not.

Unfortunately, while you can route the start-suspend command through
userspace (init, whatever) like the reboot command is, but I fear when
the suspend is in progress, it's not possible to talk to userspace
anymore ...

--
Vojtech Pavlik
SuSE Labs, SuSE CR