Overview
| Comment: | change method of launching logpro with explicit sh -c "logpro ..." to avoid unfortunate $SHELL interactions; add support for env var $LOGPRO_EXE to override logpro in $PATH if necessary to aid future debug |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | v1.65 |
| Files: | files | file ages | folders |
| SHA1: |
5cda9f73463a504d040ccce183bcfc3d |
| User & Date: | bjbarcla on 2018-05-21 16:38:14 |
| Other Links: | branch diff | manifest | tags |
Context
|
2018-05-22
| ||
| 12:39 | ! var support check-in: 0323ded23f user: mrwellan tags: v1.65 | |
|
2018-05-21
| ||
| 16:38 | change method of launching logpro with explicit sh -c "logpro ..." to avoid unfortunate $SHELL interactions; add support for env var $LOGPRO_EXE to override logpro in $PATH if necessary to aid future debug check-in: 5cda9f7346 user: bjbarcla tags: v1.65 | |
| 16:01 | updated call to execute listner script to process run as system call was bloacking the rest of the process check-in: aa94695956 user: pjhatwal tags: v1.65 | |
Changes
Modified launch.scm from [f828709706] to [f28ed7a65f]. [diff]