From: Pavel Machek <pavel@suse.cz>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
felipe_alfaro@linuxmail.org, mochel@osdl.org, george@mvista.com,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [pm] fix time after suspend-to-*
Date: Wed, 29 Oct 2003 10:43:37 +0100 [thread overview]
Message-ID: <20031029094336.GB757@elf.ucw.cz> (raw)
In-Reply-To: <16286.60534.924753.349385@wombat.chubb.wattle.id.au>
Hi!
> Stephen> On Tue, 28 Oct 2003 10:32:33 +0100 Pavel Machek
> Stephen> <pavel@suse.cz> wrote:
> Stephen> We could invent a new signal whose default action is ignore
> Stephen> ... Solaris has SIGFREEZE and SIGTHAW (the comment in the
> Stephen> header file says used by CPR - whatever that is). SIGSUSPEND
> Stephen> and SIGRESUME?
>
> CPR -- checkpoint/restart
>
> POSIX said to use SIGCKPT and SIGCONT (in at least *one* of the draft
> 1003.1m standards -- I've lost access to them recently, and the
> working group stopped working back in 2000)
>
> Suspend/resume is essentially a system-wide checkpoint+restart.
>
> Maybe use SIGCKPT and SIGCONT? Or even SIGSTOP and SIGCONT (after
> all, you're stopping the process, then restarting it)
SIGSTOP/SIGCONT is non-starter; too many apps have problem with that.
I guess Patrick's /sbin/hotplug solution is best; implement it as
kill -SIGSTOP -1 if you want to.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-10-29 9:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 23:33 [pm] fix time after suspend-to-* Pavel Machek
2003-10-22 23:52 ` john stultz
2003-10-23 8:17 ` Pavel Machek
2003-10-23 20:23 ` George Anzinger
2003-10-23 20:55 ` john stultz
2003-10-23 23:09 ` George Anzinger
2003-10-23 23:38 ` Pavel Machek
2003-10-24 0:29 ` john stultz
2003-10-24 0:39 ` john stultz
2003-10-24 2:10 ` George Anzinger
2003-10-24 7:48 ` Pavel Machek
2003-10-27 23:24 ` George Anzinger
2003-10-27 23:43 ` Patrick Mochel
2003-10-28 1:35 ` Nigel Cunningham
2003-10-28 8:33 ` Felipe Alfaro Solana
2003-10-28 9:32 ` Pavel Machek
2003-10-28 11:41 ` Stephen Rothwell
2003-10-28 12:29 ` Pavel Machek
2003-10-28 12:39 ` Stephen Rothwell
2003-10-28 22:23 ` Peter Chubb
2003-10-29 2:24 ` Valdis.Kletnieks
2003-10-29 9:43 ` Pavel Machek [this message]
2003-10-28 14:30 ` Felipe Alfaro Solana
2003-10-28 17:28 ` Pavel Machek
2003-10-28 20:16 ` Felipe Alfaro Solana
2003-10-28 21:13 ` Andreas Schwab
2003-10-28 21:29 ` George Anzinger
2003-10-29 9:38 ` Pavel Machek
2003-10-29 11:28 ` Gabriel Paubert
2003-10-29 11:55 ` PCI Bus error 6290 or 0290 Remus
2003-10-29 12:40 ` Meelis Roos
2003-10-29 12:49 ` Remus
2003-10-29 20:42 ` [pm] fix time after suspend-to-* George Anzinger
2003-10-30 9:02 ` Pavel Machek
2003-10-28 15:21 ` Valdis.Kletnieks
2003-10-28 17:26 ` Pavel Machek
2003-10-28 18:20 ` Patrick Mochel
2003-10-28 19:36 ` Valdis.Kletnieks
2003-10-28 20:19 ` Felipe Alfaro Solana
2003-10-24 7:49 ` Pavel Machek
2003-10-23 23:40 ` Pavel Machek
2003-10-27 22:43 ` Patrick Mochel
2003-10-22 23:57 ` Måns Rullgård
2003-10-29 8:20 Mathias Fröhlich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031029094336.GB757@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=felipe_alfaro@linuxmail.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=peter@chubb.wattle.id.au \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).