Page History

...

Finally, the html-ized version of the man pages should be linked from the administration guide and accessible from trafficserver.apache.org/docs.

https://issues.apache.org/jira/browse/TS-764

Command option consistency

...

All content that users should not directly interact with should not be in the $PATH. This means that commands like traffic_server should move to libexec.

Renaming user commands

I would like to rename some of the commands, eg. traffic_sac. This raises a binary compatibility problem that might not be surmountable. Generating consensus will be a problem

Reducing the number of commands

Are there opportunities to reduce the number of commands a TrafficServer user needs to know? For example, do we really need traffic_line and traffic_shell?

Improve error messages and behaviour

For example:

blacko:~ jpeach$ sudo /opt/ats/bin/traffic_shell 
[connect] ERROR (main_socket_fd 3): No such file or directory
TSInit 5: Failed to initialize MgmtAPI in /opt/ats/var/trafficserver
[connect] ERROR (main_socket_fd 23): No such file or directory
% [connect] ERROR (main_socket_fd 25): No such file or directory
[connect] ERROR (main_socket_fd 25): No such file or directory
[connect] ERROR (main_socket_fd 25): No such file or directory
...

Huh?

Bundled plugins

...

Plugins should have their own man pages documenting behaviour and configuration.