[Next-Generation Sequencing Book]

Submit | Open tickets | Closed tickets

[ Ticket #1127 ] Visual organization of install log
Date:
03/11/11 14:31
Submitted by:
B_Fristensky 		Assigned to:
umhameld
Category:
Getbirch 		Priority:
2
Ticket group:
New Feature Request 		Resolution:
Not Resolved
Summary:
Visual organization of install log
Original submission:
It would be useful if the logs had some way of visually breaking up the different sections of the install process, just to make them stand out more. For example:

================== Getbirch v1.2 ==============================
Friday, March 11, 2011 11:57:33 AM CST
getbirch.py: Running getbirch installer process
getbirch.py: Updating an existing BIRCH installation
------------------ Testing dependencies ----------------------
getbirch.py: Dependancy "csh" found: True
getbirch.py: Dependancy "java" found: True
getbirch.py: Dependancy "python" found: True
getbirch.py: The selected directory /home/frist/temp/BIRCH contains a BIRCH installation, it will be updated
------------------------ Nobirch ------------------------------
getbirch.py: Running nobirch
getbirch.py: Running in quiet mode
getbirch.py: Done!
getbirch.py: Logout and login again so that the changes can take effect.
getbirch.py: If you wish to restore BIRCH access, type
getbirch.py: /home/frist/temp/BIRCH/admin/newuser
----------------- Removing old BIRCH files --------------------
getbirch.py: Purging old BIRCH
getbirch.py: Removing old BIRCH component: labace
getbirch.py: Removing old BIRCH component: GenPept
getbirch.py: Removing old BIRCH component: script
getbirch.py: Removing old BIRCH component: install-birch
getbirch.py: Removing old BIRCH component: bin-linux-intel
getbirch.py: Removing old BIRCH component: dat
Please log in to add comments and receive followups via email.
Followups
Comment Date By
Every major task should begin with a new line separator.

Mostly, that would be each time a new script is launched like customdoc.py or htmldoc.py

I'm not too fussy about what the separators look like. Where there is a script name, then it would be good to put the name of the script into the separator, which then also becomes a search target if you want to quickly go to that script in the .log file.

As well, each time getbirch.py does something new (downloading, untaring, cleaning up) that merits a line separator. These are mainly for the purposes of making it easier to read the log files when something goes wrong. 		03/12/11 14:02 B_Fristensky
This should be an easy change to make, but I need more detail on exactly what it is that you want done.

I get the general idea from your example below, but what I need is a list of categories and what should go in each of them.

Also, what kind of line separator would you like? 		03/12/11 11:52 umhameld
No results for "Dependent on ticket"
No results for "Dependent on Task"
No other tickets are dependent on this ticket
Ticket change history
Field Old value Date By
status_id Open 03/15/11 22:16 umhameld
close_date 12/31/69 19:00 03/15/11 22:16 umhameld
priority 4 03/11/11 22:01 umhameld
status_id Pending 03/11/11 14:31 B_Fristensky
priority 5 03/11/11 14:31 B_Fristensky
assigned_to unset 03/11/11 14:31 B_Fristensky
resolution_id Unset 03/11/11 14:31 B_Fristensky

© 1998-2025 Scilico, LLC. All rights reserved.