Changes between Initial Version and Version 7 of Ticket #1291


Ignore:
Timestamp:
May 9, 2016, 1:44:09 PM (8 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1291 – Description

    initial v7  
    1717The naming is a bit inconsistent, and at first sight it's not immediately clear what the `c49bb7bf-ffc7-495b-8e13-1a5c4d8f96dc.029071.log` files are.
    1818
    19 Bang has a suggestion of using a timestamp in the file name, which I also think is more useful then either the PID or the rasserver ID. So overall my suggestion would be like this:
     19The rasserver logs should be changed to have rasserver as prefix in the file names:
    2020{{{
    21 <timestamp>.rasmgr.<pid>.log
    22 <timestamp>.rasserver.<pid1>.log
    23 <timestamp>.rasserver.<pid2>.log
    24 <timestamp>.rasserver.<pid3>.log
    25 <timestamp>.rasserver.<pid4>.log
     21rasserver.3c1bb3ad-f89a-4533-878a-2fbc99f4bb50.026737.log
     22rasserver.3e34023a-c39e-4a1d-943c-0f36966e9b44.026738.log
    2623...
    2724}}}
    28 With this we get natural sorting and grouping of the logs by creation date, and `ls -ltr` can still be used to get last modified ones.
    29 
    30 I'm not quite sure if two files can be created at the same time instant so I still included the <pid>s in the log names; if this is not the case then we can move the PID to a startup log message inside the log file. The rasserver random ID can also be a log message.