> > > Hi, all. I've just thrown together a simple daemon which allows you
> > > to configure actions to be taken upon APM suspend or resume events.
> >
> > Ouch, should not this functionality be merged into apmd?
>
> I've had a look at the beta version of apmd, and I still don't like
> it, because:
>
> - only supports one command to run at suspend time
Which should not matter that much if that command is sh -c 'a; b' ;-)
> - doesn't distinguish between user and system suspends
So fix it.
> - doesn't provide a way to disable policy (the
> sync();sleep(0);sync();sleep(1); sequence)
Fix it.
> - does not document extra features.
I'm sure this is not problem for you. Anyway, you can always fix it ;-)
> And I'm not sure that what we want is a single super daemon. A
> collection of smaller daemons might be better, since it allows people
> to pick and choose. A super daemon is bloat for those who only want
> one small feature.
That daemon is
-rwxr-xr-x 1 root root 38015 Sep 8 19:37 /usr/src/apmd.my/apmd*
38K big. Unless you have even more crappy hardware than I
(386dx40/8Meg), you can probably live pretty well with this
'bloat'. And when someone modifies /proc/apm layout, you'll go out and
modify 5 different daemons. I believe this is not the way to go.
Pavel
PS: You probably do not want 5 different bad apm daemons, one good apm
daemon is much better. BTW what you reported are bugs, and I'm pretty
sure their fixes can be easily rolled into official tree. Believe me,
it is easier than maintaining your own little daemon.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/