Opened 9 years ago
Last modified 8 years ago
#1291 closed defect
Log file names — at Initial Version
| Reported by: | Dimitar Misev | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 9.3 |
| Component: | rasmgr | Version: | development |
| Keywords: | Cc: | Peter Baumann, Bang Pham Huu, Alex Toader, Alex Dumitru, Vlad Merticariu, George Merticariu | |
| Complexity: | Medium |
Description
The logs in $RMANHOME/log look like this now:
3c1bb3ad-f89a-4533-878a-2fbc99f4bb50.026737.log 3e34023a-c39e-4a1d-943c-0f36966e9b44.026738.log 408a8ea9-9033-4a18-a168-d77c979f92fc.026730.log 583cec65-a4e6-47a6-a9e0-409d9af8469d.026736.log 645a6898-a003-4d05-a71d-9ca4d90a2ce3.026731.log 6edd0118-b6c9-4680-b6c2-bd6ff27f2203.026734.log 6ef4a634-4d75-4c9a-94df-9b4ccd374028.026735.log 77974850-a34d-464d-9219-f7d08a7efe8c.026732.log 91bfca84-0b25-43f0-8d92-29fc2c4dc527.026733.log c49bb7bf-ffc7-495b-8e13-1a5c4d8f96dc.029071.log nohup.out rasmgr.26561.log
The 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.
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:
<timestamp>.rasmgr.<pid>.log <timestamp>.rasserver.<pid1>.log <timestamp>.rasserver.<pid2>.log <timestamp>.rasserver.<pid3>.log <timestamp>.rasserver.<pid4>.log ...
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.
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.
