Not logged in
  • Log in
    Membership (41322+) Group hosting [?] Wiki
    Franklin Award

    About bioinformatics
    Bioinformatics training
    Bioinformatics jobs

    All information groups
    Online databases Online analysis tools Online education tools More tools

    All software groups
    FTP repository
    SVN & CVS repositories [?]
    Mailing lists

    News & Commentary
  • Submit
  • Archives
  • Subscribe

  • Jobs Forum
    (Career Center)
  • Submit
  • Archives
  • Subscribe
  • BIRCH: Comprehensive bioinfo. system - Support tickets

    Submit | Open tickets | Closed tickets

    [ Ticket #1127 ] Visual organization of install log
    03/11/11 14:31
    Submitted by:
    Assigned to:
    Ticket group:
    New Feature Request
    Not Resolved
    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 Running getbirch installer process Updating an existing BIRCH installation
    ------------------ Testing dependencies ---------------------- Dependancy "csh" found: True Dependancy "java" found: True Dependancy "python" found: True The selected directory /home/frist/temp/BIRCH contains a BIRCH installation, it will be updated
    ------------------------ Nobirch ------------------------------ Running nobirch Running in quiet mode Done! Logout and login again so that the changes can take effect. If you wish to restore BIRCH access, type /home/frist/temp/BIRCH/admin/newuser
    ----------------- Removing old BIRCH files -------------------- Purging old BIRCH Removing old BIRCH component: labace Removing old BIRCH component: GenPept Removing old BIRCH component: script Removing old BIRCH component: install-birch Removing old BIRCH component: bin-linux-intel Removing old BIRCH component: dat
    Please log in to add comments and receive followups via email.
    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 or

    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 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


    Copyright © 2019 · Scilico, LLC