conflicts between shutdown hooks of nvram-wakeup and e.g. noad

[Thomas Schmidt]

--AqsLC8rIMeq19msA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Tobias Grimm schrieb am 13.01.05, um 00:41 Uhr:
> The other option would be to set SHUTDOWNCMD=3D$SHUTDOWN_CMD in the=20
> shutdown script. But I think its better to go back and let SHUTDOWNCMD=20
> be the black sheep without underscore in vdr.default :) Whatever you=20
> prefer! ;)

Well, i will rename it to $SHUTDOWNCMD again, because the other way
would require nvram-wakeup to be changed also. ;-)

> BTW: Do you think its good to let VDR shutdown the system in the=20
> standard configuration at all? I mean there must be a reason, that root=
=20
> is required to shutdown. It may be better to force the administrator to=
=20
> enable shutdown by vdr, if this is needed.

Hmm, i aso thought about this, and i think it would be the best to add
a ENABLE_SHUTDOWN-variable to /etc/default/vdr, and set the default to
0 - what do you think about it?

P.S.: I want to ask Christoph to upload vdr 1.2.6-6 in a few days,
because i had a private conversation with someone, who is a little bit
annoyed that we still have not fixed the security-issues with vdr, so
i will test the packge a little bit more in the next days and if
everything is allright i want to ask Christoph for the upload.


Thomas

--=20
Thomas Schmidt
thomas.schmidt@in.stud.tu-ilmenau.de

--AqsLC8rIMeq19msA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB56RCc9+NqwoydlIRAgadAJ96b2pm/+dUv+c834b7izzVuXTyfwCgodPn
33VZJtacSdw+QP8VuNk5sJc=
=bws7
-----END PGP SIGNATURE-----

--AqsLC8rIMeq19msA--