Re: See [shell]s

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 70169
interpreted = N
texte = I think shell commands dump their output to the terminal where the command usually comes from, hence the "silence" of a shell tag (no terminal to send it to). Try capturing your output in a text variable: [text]foobar=[shell]nifty shell commands here[/Shell][/text] [foobar] Dave Hurley Manager of Departmental Computing Biology Department University of Washington On Apr 16, 2008, at 12:37 PM, Dennis J. Bonsall, Jr. wrote: > Yeah, I know, its a bad pun... > > I am having a problem with the [shell] context. Mainly, that if > there is an error, the output is suppressed. It appears as though, > if the shell script runs without an issue, that the expected output > occurs. But, if there is a problem, no output into WebDNA is > visible - you get a blank page. This makes it very difficult to > troubleshoot. Is this an issue caused by WebDNA, or do *nix > operating systems (in this case OSX) not return visible errors from > the command prompt to users that a human operator cannot log into > to see (in this case www)? Is there any way that anyone can think > of where the output to 'www' can be recorded in the event of an > error (such as a log file)? Or can 'www' be turned into a user > where I can log into it to test scripts out (without screwing > anything else up)? All permissions appear to be correct, so I do > not think that is the problem. But, it would be a lot easier to > troubleshoot if I could see what was going on. > > Anyone of you unix gurus have any ideas? > > Thanks, > Dennis > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: See [shell]s ( Marc Thompson 2008)
  2. Re: See [shell]s ( "Dennis J. Bonsall, Jr." 2008)
  3. Re: See [shell]s ( "Dennis J. Bonsall, Jr." 2008)
  4. Re: See [shell]s ( Bob Minor 2008)
  5. Re: See [shell]s ( "Dennis J. Bonsall, Jr." 2008)
  6. Re: See [shell]s ( Donovan Brooke 2008)
  7. Re: See [shell]s ( Dave Hurley 2008)
  8. See [shell]s ( "Dennis J. Bonsall, Jr." 2008)
I think shell commands dump their output to the terminal where the command usually comes from, hence the "silence" of a shell tag (no terminal to send it to). Try capturing your output in a text variable: [text]foobar=[shell]nifty shell commands here[/Shell][/text] [foobar] Dave Hurley Manager of Departmental Computing Biology Department University of Washington On Apr 16, 2008, at 12:37 PM, Dennis J. Bonsall, Jr. wrote: > Yeah, I know, its a bad pun... > > I am having a problem with the [shell] context. Mainly, that if > there is an error, the output is suppressed. It appears as though, > if the shell script runs without an issue, that the expected output > occurs. But, if there is a problem, no output into WebDNA is > visible - you get a blank page. This makes it very difficult to > troubleshoot. Is this an issue caused by WebDNA, or do *nix > operating systems (in this case OSX) not return visible errors from > the command prompt to users that a human operator cannot log into > to see (in this case www)? Is there any way that anyone can think > of where the output to 'www' can be recorded in the event of an > error (such as a log file)? Or can 'www' be turned into a user > where I can log into it to test scripts out (without screwing > anything else up)? All permissions appear to be correct, so I do > not think that is the problem. But, it would be a lot easier to > troubleshoot if I could see what was going on. > > Anyone of you unix gurus have any ideas? > > Thanks, > Dennis > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Dave Hurley

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

range searching (1998) Terry's formvariables tip (1998) problems with 2 tags (1997) IE Cache Problems... (1999) Re[2]: Images (2000) Security Issues and WebCommerce Solution (1997) Help! WebCat2 bug (1997) Max Record length restated as maybe bug (1997) Disappearing Databases (2000) Upload and WebCat (1998) OT: Web Cams (2003) Everyone: List Traffic (was [include ...] behavior) (1997) [ShowNext] (1997) WYSIWYG-editor for mac (2003) truncating email part II (1997) off topic - dna snipets (1997) Pithy questions on webcommerce & siteedit (1997) webmerch and serials - almost there (1997) printing twice? and fix (1997) Re:no [search] with NT (1997)