Re: See [shell]s

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 70170
interpreted = N
texte = 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 Hi Dennis, Are you seeing anything in the source of the "blank page" when this occurs? Are you sure you have isolated the "blank page" problem to a [shell] error? My reasoning is that if you have code that results in a missing end [text] context, or code that is missing an HTML ending element, you can get the "blank page" syndrome. Other than that, I've only used [shell] in a limited fashion... however, wouldn't a failing shell command record to standard error logs? Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE EUCA Design Center <- Web Development, DTP, Consulting, and Labels -> <- Fabricated Art (Metal, Glass, Kustom Paint) -> PH:> (608) 770-3822 | FAX:>(608) 291-2024 WEB:> http://www.euca.us & http://www.egg.bz =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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)
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 Hi Dennis, Are you seeing anything in the source of the "blank page" when this occurs? Are you sure you have isolated the "blank page" problem to a [shell] error? My reasoning is that if you have code that results in a missing end [text] context, or code that is missing an HTML ending element, you can get the "blank page" syndrome. Other than that, I've only used [shell] in a limited fashion... however, wouldn't a failing shell command record to standard error logs? Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE EUCA Design Center <- Web Development, DTP, Consulting, and Labels -> <- Fabricated Art (Metal, Glass, Kustom Paint) -> PH:> (608) 770-3822 | FAX:>(608) 291-2024 WEB:> http://www.euca.us & http://www.egg.bz =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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/ Donovan Brooke

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:

[searchString] (1997) Can't use old cart file (was One more try) (1997) Field name-subcategory (1997) WCS Newbie question (1997) Forms Search Questions (1997) Shownext never shows next...still (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Weird problems with [SHOWIF]s (1997) WebCat 4.0.1 HTTP_REFERRER over 255 char bug (2000) checksum for Discover credit cards (1999) EmailProblem (2003) Searching multiple fields from one form field (1997) Formulas.db not working (2006) WebCatalog NT beta 18 problem (1997) 4.x code problem. (2000) Upgrading old WebCat Database Files (1997) WebCat b13 CGI -shownext- (1997) Opposite of Summ=T? (2000) [OT] Apple and 128bit SSL (2003) Webmerchant quitting (1998)