This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2F3CC51A4B2841E627D47D72
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steven M. Bellovin wrote:
> On Sat, 01 Jul 2006 13:18:27 +0000, "Thomas E. Spanjaard"
> <tgen@netphreax.net> wrote:
>>Steven M. Bellovin wrote:
>>>	temp=acpitemp	 >70*2	   /bin/shutdown -p now
>>>where the *2 indicates that it has to happen twice in a row.  A few more
>>>frills, like shell variables for each config line -- the 'temp' means that
>>>a script would be run with envstatd_temp set to the value.  A | at the
>>>start of the command would create a pipeline that would be fed the value
>>>on stdin, to permit easy real-time graphing programs.
>>Confusing, using mathematical symbols for other meanings. Isn't the 
>>how-many-times-or-how-long (as Jachym Holecek suggested) better off in a 
>>separate column (think inetd.conf syntax)? Come to think of it, 
>>inetd.conf is a viable example format for this.
> I thought about that; it's certainly one perspective.  Here, though, I
> assumed that it would rarely be used, in which case I'm imposing a burden
> on everything else.  The other option is something like '-n 2', but that
> might be even more confusing.

Hmm, but a crontab is similar to this as well, but allows you to use * 
in separate columns (so no binary operator use is associated with the 
symbol due to obvious distance between columns) in the case where you 
don't want to specify anything specific.

Cheers,
-- 
         Thomas E. Spanjaard
         tgen@netphreax.net

--------------enig2F3CC51A4B2841E627D47D72
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFEppCk6xCMwBJ+1+sRA2akAJ4zVCK8lZ8f1xIBu7mRrC7/U5+0UwCePzEY
rz1mTdx20U2OGWaD1n7MmrQ=
=du+B
-----END PGP SIGNATURE-----

--------------enig2F3CC51A4B2841E627D47D72--