On Sun, 2009-01-25 at 18:53 +0100, Marco d'Itri wrote: > On Jan 25, Gabriel Burt <gburt@xxxxxxxxxx> wrote: > > > On Sun, 2009-01-25 at 17:44 +0100, Marco d'Itri wrote: > > > People usually want to use pm-utils to suspend the system instead of > > > the raw kernel interface, so I added an option to just exit after > > > configuring the wakeup time. > > > Isn't this what the "on" option did already? > No, "on" keeps waiting until the alarm fires. Even worse, if you do > something like "rtcwake -m on -s 60 & pm-utils suspend" then rtcwake > will miss the event and stay around forever keeping the rtc fd open and > preventing other applications from accessing it. > I am not attached to these changes, but something is needed to make > rtcwake actually useful. I can't see how it could be used with pm-utils > in its present form nor the use cases for directly accessing the kernel > suspend interface. I got pm-utils to use rtcwake by calling out to it in a pm-utils hooks like this: sh -c "$rtcwake_cmd -m on -s $seconds_from_now &" Gabriel -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
