David,
I think you may have accidentally committed a change to startofbiz.sh -- the line to run it in background with a "&" is commented out, and it now runs in the command line. Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
This was actually intentional, though if the consensus is against it I can certainly change it back. This script has 2 run lines in it with one commented out, and before the default one was the more production oriented one, though pretty much the rest of OFBiz directly out of SVN is more development oriented (including default cache settings and so on). I didn't think anyone using it for production purposes would generally mind too much as it is usually necessary to edit this script anyway for memory and sometimes other settings as well. I may be wrong though... -David Si Chen wrote: > David, > > I think you may have accidentally committed a change to startofbiz.sh -- > the line to run it in background with a "&" is commented out, and it now > runs in the command line. > > Si > > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
David,
The advantage of running it background and piping it to a log is that some window terminals don't scroll far back enough. This was a real problem with the Windows CMD terminal but also happens with xterm as well. It's OK though if you want to keep the other one as the default. Si David E Jones wrote: This was actually intentional, though if the consensus is against it I can certainly change it back. This script has 2 run lines in it with one commented out, and before the default one was the more production oriented one, though pretty much the rest of OFBiz directly out of SVN is more development oriented (including default cache settings and so on). I didn't think anyone using it for production purposes would generally mind too much as it is usually necessary to edit this script anyway for memory and sometimes other settings as well. I may be wrong though... -David Si Chen wrote:David, I think you may have accidentally committed a change to startofbiz.sh -- the line to run it in background with a "&" is commented out, and it now runs in the command line. Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
I guess kind of an interesting debate... In development is it better to have the log spewn out on the console or to watch in a log file when needed... For developers I'd actually like to see everything glancing at the log during start up because there are issues that creep in on occasion that could be avoided by doing so. Of course, if you don't have a good terminal to run things in or a good way to watch the logs coming from a file then that's an issue... It's actually one reason I hate Windows and in spite of the pain I used to use Cygwin for my terminal because it is so much better than the Windows CMD thingy. I guess if anyone has other ideas, or is bored (or frustrated with whatever they're working on...) and wants to type something that doesn't require too much thought, I'd be interested in hearing them. -David Si Chen wrote: > David, > > The advantage of running it background and piping it to a log is that > some window terminals don't scroll far back enough. This was a real > problem with the Windows CMD terminal but also happens with xterm as > well. It's OK though if you want to keep the other one as the default. > > Si > > David E Jones wrote: >> This was actually intentional, though if the consensus is against it I can certainly change it back. This script has 2 run lines in it with one commented out, and before the default one was the more production oriented one, though pretty much the rest of OFBiz directly out of SVN is more development oriented (including default cache settings and so on). >> >> I didn't think anyone using it for production purposes would generally mind too much as it is usually necessary to edit this script anyway for memory and sometimes other settings as well. I may be wrong though... >> >> -David >> >> >> Si Chen wrote: >> >>> David, >>> >>> I think you may have accidentally committed a change to startofbiz.sh -- >>> the line to run it in background with a "&" is commented out, and it now >>> runs in the command line. >>> >>> Si >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [hidden email] >>> http://lists.ofbiz.org/mailman/listinfo/dev >>> >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> >> >> > > ------------------------------------------------------------------------ > > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
David, Si,
I'd prefer to see every possible startup method spewing out logs by default. I've seen developers (especially OFBiz newbies) get a bit baffled on a number of occasions because they switch between "startofbiz.sh" and "ant run". A consistent behaviour on startup can only be a good thing. I do sympathise with those poor souls stuck with the Win CMD thing, but generally I find I've memorised the output before it runs out the top of the buffer in XP, such is the blistering performance! Although sometimes it's hard to concentrate on the logs with all the clippy-esque interruptions! :-) I seem to be turning into a windows-basher! I'm off to grow a big beard! -- Kind Regards Andrew Sykes <[hidden email]> Sykes Development Ltd http://www.sykesdevelopment.com _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
In reply to this post by David E. Jones
How 'bout making it dependant on an environment variable?
If [ "$OFBIZ_BACKGROUND" != "" ] ; then <use background launch> else <use foreground launch> fi Than the script doesn't need to change between implementations. Carl On Monday, May 01, 2006 18:17, David E Jones wrote: > I guess kind of an interesting debate... In development is it better to > have the log spewn out on the console or to watch in a log file when > needed... > > For developers I'd actually like to see everything glancing at the log > during start up because there are issues that creep in on occasion that > could be avoided by doing so. > > Of course, if you don't have a good terminal to run things in or a good way > to watch the logs coming from a file then that's an issue... It's actually > one reason I hate Windows and in spite of the pain I used to use Cygwin for > my terminal because it is so much better than the Windows CMD thingy. > > I guess if anyone has other ideas, or is bored (or frustrated with whatever > they're working on...) and wants to type something that doesn't require too > much thought, I'd be interested in hearing them. > > -David > > Si Chen wrote: > > David, > > > > The advantage of running it background and piping it to a log is that > > some window terminals don't scroll far back enough. This was a real > > problem with the Windows CMD terminal but also happens with xterm as > > well. It's OK though if you want to keep the other one as the default. > > > > Si > > > > David E Jones wrote: > >> This was actually intentional, though if the consensus is against it I > >> can certainly change it back. This script has 2 run lines in it with one > >> commented out, and before the default one was the more production > >> oriented one, though pretty much the rest of OFBiz directly out of SVN > >> is more development oriented (including default cache settings and so > >> on). > >> > >> I didn't think anyone using it for production purposes would generally > >> mind too much as it is usually necessary to edit this script anyway for > >> memory and sometimes other settings as well. I may be wrong though... > >> > >> -David > >> > >> Si Chen wrote: > >>> David, > >>> > >>> I think you may have accidentally committed a change to startofbiz.sh > >>> -- the line to run it in background with a "&" is commented out, and it > >>> now runs in the command line. > >>> > >>> Si > >>> > >>> > >>> _______________________________________________ > >>> Dev mailing list > >>> [hidden email] > >>> http://lists.ofbiz.org/mailman/listinfo/dev > >> > >> _______________________________________________ > >> Dev mailing list > >> [hidden email] > >> http://lists.ofbiz.org/mailman/listinfo/dev > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > Dev mailing list > > [hidden email] > > http://lists.ofbiz.org/mailman/listinfo/dev > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
In reply to this post by David E. Jones
David,
It works for me when I do a: $ startofbiz.sh Then a $ tail -f logs/console.log So it does both. This works in Linux or OS X. As for Windows, who knows? Si David E Jones wrote: I guess kind of an interesting debate... In development is it better to have the log spewn out on the console or to watch in a log file when needed... For developers I'd actually like to see everything glancing at the log during start up because there are issues that creep in on occasion that could be avoided by doing so. Of course, if you don't have a good terminal to run things in or a good way to watch the logs coming from a file then that's an issue... It's actually one reason I hate Windows and in spite of the pain I used to use Cygwin for my terminal because it is so much better than the Windows CMD thingy. I guess if anyone has other ideas, or is bored (or frustrated with whatever they're working on...) and wants to type something that doesn't require too much thought, I'd be interested in hearing them. -David Si Chen wrote:David, The advantage of running it background and piping it to a log is that some window terminals don't scroll far back enough. This was a real problem with the Windows CMD terminal but also happens with xterm as well. It's OK though if you want to keep the other one as the default. Si David E Jones wrote:This was actually intentional, though if the consensus is against it I can certainly change it back. This script has 2 run lines in it with one commented out, and before the default one was the more production oriented one, though pretty much the rest of OFBiz directly out of SVN is more development oriented (including default cache settings and so on). I didn't think anyone using it for production purposes would generally mind too much as it is usually necessary to edit this script anyway for memory and sometimes other settings as well. I may be wrong though... -David Si Chen wrote:David, I think you may have accidentally committed a change to startofbiz.sh -- the line to run it in background with a "&" is commented out, and it now runs in the command line. Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev------------------------------------------------------------------------ _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
windows would be...
startofbiz.bat > logs\console.log --- Si Chen <[hidden email]> wrote: > David, > > It works for me when I do a: > > $ startofbiz.sh > > Then a > $ tail -f logs/console.log > > So it does both. This works in Linux or OS X. As > for Windows, who knows? > > Si > > David E Jones wrote: > > I guess kind of an interesting debate... In > development is it better to have the log spewn out > on the console or to watch in a log file when > needed... > > > > For developers I'd actually like to see everything > glancing at the log during start up because there > are issues that creep in on occasion that could be > avoided by doing so. > > > > Of course, if you don't have a good terminal to > run things in or a good way to watch the logs coming > from a file then that's an issue... It's actually > one reason I hate Windows and in spite of the pain I > used to use Cygwin for my terminal because it is so > much better than the Windows CMD thingy. > > > > I guess if anyone has other ideas, or is bored (or > frustrated with whatever they're working on...) and > wants to type something that doesn't require too > much thought, I'd be interested in hearing them. > > > > -David > > > > > > Si Chen wrote: > > > >> David, > >> > >> The advantage of running it background and piping > it to a log is that > >> some window terminals don't scroll far back > enough. This was a real > >> problem with the Windows CMD terminal but also > happens with xterm as > >> well. It's OK though if you want to keep the > other one as the default. > >> > >> Si > >> > >> David E Jones wrote: > >> > >>> This was actually intentional, though if the > consensus is against it I can certainly change it > back. This script has 2 run lines in it with one > commented out, and before the default one was the > more production oriented one, though pretty much the > rest of OFBiz directly out of SVN is more > development oriented (including default cache > settings and so on). > >>> > >>> I didn't think anyone using it for production > purposes would generally mind too much as it is > usually necessary to edit this script anyway for > memory and sometimes other settings as well. I may > be wrong though... > >>> > >>> -David > >>> > >>> > >>> Si Chen wrote: > >>> > >>> > >>>> David, > >>>> > >>>> I think you may have accidentally committed a > change to startofbiz.sh -- > >>>> the line to run it in background with a "&" is > commented out, and it now > >>>> runs in the command line. > >>>> > >>>> Si > >>>> > >>>> > >>>> _______________________________________________ > >>>> Dev mailing list > >>>> [hidden email] > >>>> http://lists.ofbiz.org/mailman/listinfo/dev > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> Dev mailing list > >>> [hidden email] > >>> http://lists.ofbiz.org/mailman/listinfo/dev > >>> > >>> > >>> > >>> > >> > > >> > >> > >> _______________________________________________ > >> Dev mailing list > >> [hidden email] > >> http://lists.ofbiz.org/mailman/listinfo/dev > >> > > > > _______________________________________________ > > Dev mailing list > > [hidden email] > > http://lists.ofbiz.org/mailman/listinfo/dev > > > > > > > > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Is there a command that displays the log file like the unix tail?
Chris Howe wrote: windows would be... startofbiz.bat > logs\console.log --- Si Chen [hidden email] wrote:David, It works for me when I do a: $ startofbiz.sh Then a $ tail -f logs/console.log So it does both. This works in Linux or OS X. As for Windows, who knows? Si David E Jones wrote:I guess kind of an interesting debate... Indevelopment is it better to have the log spewn out on the console or to watch in a log file when needed...For developers I'd actually like to see everythingglancing at the log during start up because there are issues that creep in on occasion that could be avoided by doing so.Of course, if you don't have a good terminal torun things in or a good way to watch the logs coming from a file then that's an issue... It's actually one reason I hate Windows and in spite of the pain I used to use Cygwin for my terminal because it is so much better than the Windows CMD thingy.I guess if anyone has other ideas, or is bored (orfrustrated with whatever they're working on...) and wants to type something that doesn't require too much thought, I'd be interested in hearing them.-David Si Chen wrote:David, The advantage of running it background and pipingit to a log is thatsome window terminals don't scroll far backenough. This was a realproblem with the Windows CMD terminal but alsohappens with xterm aswell. It's OK though if you want to keep theother one as the default.Si David E Jones wrote:This was actually intentional, though if theconsensus is against it I can certainly change it back. This script has 2 run lines in it with one commented out, and before the default one was the more production oriented one, though pretty much the rest of OFBiz directly out of SVN is more development oriented (including default cache settings and so on).I didn't think anyone using it for productionpurposes would generally mind too much as it is usually necessary to edit this script anyway for memory and sometimes other settings as well. I may be wrong though...-David Si Chen wrote:David, I think you may have accidentally committed achange to startofbiz.sh --the line to run it in background with a "&" iscommented out, and it nowruns in the command line. Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev------------------------------------------------------------------------_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
In reply to this post by Si Chen-2
On Mon, 1 May 2006, Si Chen wrote:
> David, > > The advantage of running it background and piping it to a log is that > some window terminals don't scroll far back enough. This was a real > problem with the Windows CMD terminal but also happens with xterm as > well. It's OK though if you want to keep the other one as the default. Increase your scrollback for xterm. It's a simple cmdline option. _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
In reply to this post by Si Chen-2
On 5/2/06, Si Chen <[hidden email]> wrote:
> David, > > It works for me when I do a: > > $ startofbiz.sh > > Then a > $ tail -f logs/console.log > > So it does both. This works in Linux or OS X. As for Windows, who knows? As another option, the 'tee' command could be employed in the script itself to write to both stdout and a log file. Ciao, -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
What about ending the script in exec tail -f logs/console.log? Maybe a test for
tail command too. - Leon David Welton wrote: > On 5/2/06, Si Chen <[hidden email]> wrote: >> David, >> >> It works for me when I do a: >> >> $ startofbiz.sh >> >> Then a >> $ tail -f logs/console.log >> >> So it does both. This works in Linux or OS X. As for Windows, who knows? > > As another option, the 'tee' command could be employed in the script > itself to write to both stdout and a log file. > > Ciao, > -- > David N. Welton > - http://www.dedasys.com/davidw/ > > Linux, Open Source Consulting > - http://www.dedasys.com/ > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Free forum by Nabble | Edit this page |