xpra icon
Bug tracker and wiki

Opened 5 months ago

Closed 5 months ago

#1865 closed enhancement (wontfix)

Archiving of logs

Reported by: stdedos Owned by: Antoine Martin
Priority: minor Milestone:
Component: server Version: 2.3.x
Keywords: Cc:

Description

Inspired by #1837 (and other bugtracking I've been doing), would it make sense to archive logs in some fashion, and symlink them to the :XX.log files?

It is possible that I will run a specific (same) command multiple times (both from server and client).
Obviously, for the case that you collect logs asap and/or have immediate access to both client and server, it doesn't matter;
however, what if I can only collect logs at a later time and/or session has overriden the previous one (e.g. because of a server crash + restart).

In a "related fashion", if I start an application with xpra, stdout leads with Saving to /run/[...]/S####.log, and then, automagically that becomes a :##.log file
(I don't remember if it's still on stdout, or I follow the /run/[...]/S####.log file and then see it)

Change History (1)

comment:1 Changed 5 months ago by Antoine Martin

Resolution: wontfix
Status: newclosed

This can be solved with scripts when you run your start commands.

and then, automagically that becomes a :##.log file

It renames the log files once it knows the actual display number.
This only applies when you don't specify a display number on the command line.

Note: See TracTickets for help on using tickets.