|-s||The script file describing the flows to be sent by the rude program. See ../rude/DOC/example.cfg, for an example.|
|-h||Print a short help.|
|-v||Print the version information.|
Set the process in real-time round-robin scheduling with the given
priority. Needs root permission. Use with care.
Every configuration file should contain at least three (3) commands: the START , one flow ON and one flow OFF command. If that requirement is not met or the parser can not recognize all the given commands in the file, the configuration file will be considered corrupted and the program will exit without any further action.
Lines starting with # or empty lines are treated as comments (i.e. are not processed). Configuration file can hold any number of comment lines anywhere in the file.
The START command must be the 1st command in the configuration file. It may be preceded with comment lines, but nothing else. If your config file has more than one (1) START command, the parsing will fail and the program will exit with error.
Configuration file should hold at least two commands for each flow: the ON and OFF commands. Between the ON and OFF commands can be random/any number of MODIFY commands, which alter the flow behaviour. Note that MODIFY commands are not available for every flow type.
Commands for each flow must be ordered according to the time - i.e. the ON command must be the 1st command for the specific flow and the MODIFY commands must be ordered by the time-field. The OFF command must be the last command for the flow. The commands for each flow can be "mixed" or each flow can have their configuration on different segment in the file. See ../rude/DOC/README.rude for detailed information on the configuration file.
Support more flow types.
I hear them crawling in my head.
Please report any other bugs to the authors.
Juha Laine, TUT <firstname.lastname@example.org> and Sampo Saaristo, TUT <email@example.com> and Rui Prior, <firstname.lastname@example.org>