terminal-logging

Registered by Pablo Catalina

It's a great idea to add a profile configuration to log the terminal output into a logfile.

The filename specification could have some special variables, for example:

* strftime
* USER (current user)
* PID (pid of the bash session: shell PID)
* PPID (pid of the terminator proccess)
...

Example:

/var/log/terminator-logs/%Y/%M/%d/$USER-%T.log

That generates a structure like:

/var/log/terminator-logs/2012/11/21/root-13:47:21.log
/var/log/terminator-logs/2012/11/21/myuser-13:47:21.log

I think, the created directories must have permisions like /tmp (1777 or rwxrwxrwt) -> with a configuration option (True/False)
 and the log files must have restricted permisions like (640 or rw-r-----).

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Stephen Boddy

Related branches

Sprints

Whiteboard

I'd add a variable that can be passed via a command line parameter.
That would help finding a specific terminator's latest/given output by an external script.
Definitely add a commandline option to enable/disable logging.

what about
terminator -e "/usr/bin/script -f /tmp/term_shell/term_shell_output"

[SJB - the current maintainer] This is a feature request, not a blueprint. If you still want this raise it as a bug and it will be marked as a feature.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.