Re: [WebDNA] 6.2 Monitor
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108189
interpreted = N
texte = > Thank you for the response. I'll go in and purchase 100 domains, and = pray it works. One last question. on your site you have: >=20 > "You can buy 1, 10 or 100 certificates. The certificates are delivered = to you through a domain name provisioning system. An accelerator = certificate is generated for every domain name and the same certificate = will also run for any associated subdomain. Each certificate is unique." >=20 > Do I have to provide all the domain names up front, or can I do them = as I go forward with each domain, using one as a test center(ie: = tes.domain.com), then switch it over to realdomain.com after. All on the = same IP of course. In other words, I want to purchase 100 certificates, = and worry about the domain they are assigned to after. No need to provide all the domain names up front; you can buy 100 = certificates and use them next year if you want, or one at a time. You = only want a certificate once a website is in production, and if you have = regular traffic on your website, you do not even need a certificate: you = can run WebbDNA 7.0 as freeware and keep your certificates for busy = websites. - chris >=20 > Rob >=20 >=20 > On Jan 23, 2012, at 2:00 PM, christophe.billiottet@webdna.us wrote: >=20 >>=20 >> On Jan 23, 2012, at 17:30, Rob wrote: >>=20 >>> I haven't yet, and just now downloaded it. Can 7 run parallel with = 6.2 on the same box? >>=20 >> yes, provided 6.2 and 7.0 do not share the same extensions. For = instance, you could run .dna with WebDNA 7.0 and .tpl with WebDNA 6.2 >>=20 >>=20 >>> ...and... can all the testing be done before the domain is pointed = to it, as I see in the instructions it needs a vhost pointed to it.=20 >>=20 >> yes, using a dedicated IP. If you run vhosts that share the same IP, = then you will need a domain name. >>=20 >>> Can that vhost be changed after everything is setup back to the = primary domain for that site? >>=20 >>=20 >> yes >>=20 >> - chris >>=20 >>>=20 >>> Rob >>>=20 >>> On Jan 23, 2012, at 1:22 PM, christophe.billiottet@webdna.us wrote: >>>=20 >>>> About the stores... since the commerce tags are still available = under 7.0 (except the URL command system) did anyone try to run a store = with 7.0? >>>>=20 >>>> - chris >>>>=20 >>>>=20 >>>>=20 >>>> On Jan 23, 2012, at 14:26, Rob wrote: >>>>=20 >>>>> Hi Chris, >>>>>=20 >>>>> I would, but won't that kill all my stores, as I am running 6.2. = Would I have to do a rewrite on everything? >>>>>=20 >>>>> That would take weeks.... :-( >>>>>=20 >>>>> Rob >>>>>=20 >>>>>=20 >>>>> On Jan 23, 2012, at 10:24 AM, christophe.billiottet@webdna.us = wrote: >>>>>=20 >>>>>> Hi Rob! download the last version of WebDNA 7.0.623 at = http://dev.webdna.us/products.html and check the history at = http://www.webdna.us/page.dna?numero=3D299 >>>>>>=20 >>>>>> This bug only affects OS X and busy servers. >>>>>>=20 >>>>>> - chris >>>>>>=20 >>>>>>=20 >>>>>> On Jan 23, 2012, at 13:25, Rob wrote: >>>>>>=20 >>>>>>> Ok, this acted up again, and am not getting errors in the debug, = or any error logs, which is strange. The processor just climbed to 180% = on the WebCatalog process. I am getting a few lines in the signal = termination log, but that's it, and a couple of them were probably = generated by me trying to get it to start. >>>>>>>=20 >>>>>>> ---Mon Jan 23 06:03:56 2012 MST Processid 66785 receive SIGTERM: >>>>>>> ---Mon Jan 23 07:56:02 2012 MST Processid 66958 receive SIGTERM: >>>>>>> ---Mon Jan 23 07:59:02 2012 MST Processid 69107 receive SIGTERM: >>>>>>>=20 >>>>>>> However, I am getting a weird error when I trigger = /Library/WebServer/CGI-Executables/WebCatalogEngine/WebCatalogCtl = restart in terminal. I get about ten or twelve lines of: >>>>>>>=20 >>>>>>> "sem_open failed: returned ENOSPC: No space left on device" >>>>>>>=20 >>>>>>> and can't exit terminal without quitting it. >>>>>>>=20 >>>>>>> Not sure at all what that error is, any ideas? The server has = 450 gigs of free space(Mac os x 10.6.8, WebDNA 6.2). I did do an = uninstall, and complete reinstall of WebDNA, but it still comes up with = this same error on restart. WebDNA does start and run normally though. >>>>>>>=20 >>>>>>> We will eventually move over to version 7, but can't get at it = for a few months, so need to get this stable for now, or at least to the = point where we don't have to babysit it. >>>>>>>=20 >>>>>>> Rob >>>>>>>=20 >>>>>>>=20 >>>>>>> On Jan 19, 2012, at 5:55 AM, Rob wrote: >>>>>>>=20 >>>>>>>> Hi Robert >>>>>>>>=20 >>>>>>>> On Jan 18, 2012, at 8:27 PM, Robert Minor wrote: >>>>>>>>=20 >>>>>>>>> Maybe the thought he was funny.=20 >>>>>>>>>=20 >>>>>>>>> Was your old server intel based?=20 >>>>>>>>=20 >>>>>>>> No, it was PPC... 10.4.11 >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> did you turn on the troubleshooting tools? >>>>>>>>=20 >>>>>>>> Yes, they are on now... Hoping to catch it the next time it = happens. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Rob >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> On Jan 18, 2012, at 6:37 PM, Rob wrote: >>>>>>>>>=20 >>>>>>>>>> Uuuuh...the server is only six months old.... how new do you = want me to try?... All that's happened is we retired an old server, that = wasn't having any problems, but it was over 5 years old, and we just = didn't trust it any more, and to replace internal hardware would cost = more then purchasing a new one. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Rob >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: >>>>>>>>>>=20 >>>>>>>>>>> Try a new server. Worked wonders for me. >>>>>>>>>>>=20 >>>>>>>>>>> Bill >>>>>>>>>>>=20 >>>>>>>>>>> On Wed, Jan 18, 2012 at 11:18 AM, Rob
= wrote: >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>> Rob wrote: >>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Very rarely(once every couple months) I have WebDNA 6.2 = stop, and drive >>>>>>>>>>>> the CPU nuts on Snow Leopard Server, and am looking at = adding a script to >>>>>>>>>>>> keep an eye on it while I go on vacation. I found an old = script... not sure >>>>>>>>>>>> where it come from or where I got it, but I had it on one = of the old >>>>>>>>>>>> servers, and would like to get it working using launchd to = start it, which >>>>>>>>>>>> isn't the problem. When I trigger the script, it comes up = with "ps: No user >>>>>>>>>>>> named 'x'". Which is fairly obvious to those who no about = these scripts, >>>>>>>>>>>> which I don't. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> So my question is, does anyone know how to get this = working, or is >>>>>>>>>>>> there a better way? ... Script below. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Rob >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I wouldn't use that script for a couple reasons. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> First, It's not bad if your server shoots up to a 145% = usage (2 CPU's) >>>>>>>>>>>> for short instances now and then.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Second, kill -9 is *not* a good way of stopping WebDNA... = at least not >>>>>>>>>>>> for 6.2 which still uses WebDNAMonitor. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Anyway, the script seems to contain logical problems in my = opinion. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> If you were to use it, I'd change it to 199%... and change = the 'kill -9' >>>>>>>>>>>> to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl = restart'. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> To fix the script, there is a change to how 'ps' functions = in Snow >>>>>>>>>>>> Leopard.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> basically change the instances of "ps -aux" in your script = to "ps aux". >>>>>>>>>>>>>=20 >>>>>>>>>>>>> To fix your CPU issue, I'd start looking into standard = troubleshooting >>>>>>>>>>>> techniques.. looking at logs, looking for overgrown log = files etc.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Donovan >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> Thanks for the input Donovan. >>>>>>>>>>>>=20 >>>>>>>>>>>> I'm not sure if I'm going to use it or not, at this point. = Its just an >>>>>>>>>>>> avenue I'm looking at, unless there is a better solution. I = did notice, >>>>>>>>>>>> however, that when WebDNA dies, the CPU hoovers around 60%, = so I'm not sure >>>>>>>>>>>> this will even work when it acts up. >>>>>>>>>>>>=20 >>>>>>>>>>>> I've been looking at the logs trying to pin out down, but = it happens so >>>>>>>>>>>> rarely that its hard to get a handle on it... :-( .. I = think all turn on >>>>>>>>>>>> everything in the Prefs Technical section for a while to = see if I can catch >>>>>>>>>>>> it. >>>>>>>>>>>>=20 >>>>>>>>>>>> Rob >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
> Thank you for the response. I'll go in and purchase 100 domains, and = pray it works. One last question. on your site you have: >=20 > "You can buy 1, 10 or 100 certificates. The certificates are delivered = to you through a domain name provisioning system. An accelerator = certificate is generated for every domain name and the same certificate = will also run for any associated subdomain. Each certificate is unique." >=20 > Do I have to provide all the domain names up front, or can I do them = as I go forward with each domain, using one as a test center(ie: = tes.domain.com), then switch it over to realdomain.com after. All on the = same IP of course. In other words, I want to purchase 100 certificates, = and worry about the domain they are assigned to after. No need to provide all the domain names up front; you can buy 100 = certificates and use them next year if you want, or one at a time. You = only want a certificate once a website is in production, and if you have = regular traffic on your website, you do not even need a certificate: you = can run WebbDNA 7.0 as freeware and keep your certificates for busy = websites. - chris >=20 > Rob >=20 >=20 > On Jan 23, 2012, at 2:00 PM, christophe.billiottet@webdna.us wrote: >=20 >>=20 >> On Jan 23, 2012, at 17:30, Rob wrote: >>=20 >>> I haven't yet, and just now downloaded it. Can 7 run parallel with = 6.2 on the same box? >>=20 >> yes, provided 6.2 and 7.0 do not share the same extensions. For = instance, you could run .dna with WebDNA 7.0 and .tpl with WebDNA 6.2 >>=20 >>=20 >>> ...and... can all the testing be done before the domain is pointed = to it, as I see in the instructions it needs a vhost pointed to it.=20 >>=20 >> yes, using a dedicated IP. If you run vhosts that share the same IP, = then you will need a domain name. >>=20 >>> Can that vhost be changed after everything is setup back to the = primary domain for that site? >>=20 >>=20 >> yes >>=20 >> - chris >>=20 >>>=20 >>> Rob >>>=20 >>> On Jan 23, 2012, at 1:22 PM, christophe.billiottet@webdna.us wrote: >>>=20 >>>> About the stores... since the commerce tags are still available = under 7.0 (except the URL command system) did anyone try to run a store = with 7.0? >>>>=20 >>>> - chris >>>>=20 >>>>=20 >>>>=20 >>>> On Jan 23, 2012, at 14:26, Rob wrote: >>>>=20 >>>>> Hi Chris, >>>>>=20 >>>>> I would, but won't that kill all my stores, as I am running 6.2. = Would I have to do a rewrite on everything? >>>>>=20 >>>>> That would take weeks.... :-( >>>>>=20 >>>>> Rob >>>>>=20 >>>>>=20 >>>>> On Jan 23, 2012, at 10:24 AM, christophe.billiottet@webdna.us = wrote: >>>>>=20 >>>>>> Hi Rob! download the last version of WebDNA 7.0.623 at = http://dev.webdna.us/products.html and check the history at = http://www.webdna.us/page.dna?numero=3D299 >>>>>>=20 >>>>>> This bug only affects OS X and busy servers. >>>>>>=20 >>>>>> - chris >>>>>>=20 >>>>>>=20 >>>>>> On Jan 23, 2012, at 13:25, Rob wrote: >>>>>>=20 >>>>>>> Ok, this acted up again, and am not getting errors in the debug, = or any error logs, which is strange. The processor just climbed to 180% = on the WebCatalog process. I am getting a few lines in the signal = termination log, but that's it, and a couple of them were probably = generated by me trying to get it to start. >>>>>>>=20 >>>>>>> ---Mon Jan 23 06:03:56 2012 MST Processid 66785 receive SIGTERM: >>>>>>> ---Mon Jan 23 07:56:02 2012 MST Processid 66958 receive SIGTERM: >>>>>>> ---Mon Jan 23 07:59:02 2012 MST Processid 69107 receive SIGTERM: >>>>>>>=20 >>>>>>> However, I am getting a weird error when I trigger = /Library/WebServer/CGI-Executables/WebCatalogEngine/WebCatalogCtl = restart in terminal. I get about ten or twelve lines of: >>>>>>>=20 >>>>>>> "sem_open failed: returned ENOSPC: No space left on device" >>>>>>>=20 >>>>>>> and can't exit terminal without quitting it. >>>>>>>=20 >>>>>>> Not sure at all what that error is, any ideas? The server has = 450 gigs of free space(Mac os x 10.6.8, WebDNA 6.2). I did do an = uninstall, and complete reinstall of WebDNA, but it still comes up with = this same error on restart. WebDNA does start and run normally though. >>>>>>>=20 >>>>>>> We will eventually move over to version 7, but can't get at it = for a few months, so need to get this stable for now, or at least to the = point where we don't have to babysit it. >>>>>>>=20 >>>>>>> Rob >>>>>>>=20 >>>>>>>=20 >>>>>>> On Jan 19, 2012, at 5:55 AM, Rob wrote: >>>>>>>=20 >>>>>>>> Hi Robert >>>>>>>>=20 >>>>>>>> On Jan 18, 2012, at 8:27 PM, Robert Minor wrote: >>>>>>>>=20 >>>>>>>>> Maybe the thought he was funny.=20 >>>>>>>>>=20 >>>>>>>>> Was your old server intel based?=20 >>>>>>>>=20 >>>>>>>> No, it was PPC... 10.4.11 >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> did you turn on the troubleshooting tools? >>>>>>>>=20 >>>>>>>> Yes, they are on now... Hoping to catch it the next time it = happens. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Rob >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> On Jan 18, 2012, at 6:37 PM, Rob wrote: >>>>>>>>>=20 >>>>>>>>>> Uuuuh...the server is only six months old.... how new do you = want me to try?... All that's happened is we retired an old server, that = wasn't having any problems, but it was over 5 years old, and we just = didn't trust it any more, and to replace internal hardware would cost = more then purchasing a new one. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Rob >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: >>>>>>>>>>=20 >>>>>>>>>>> Try a new server. Worked wonders for me. >>>>>>>>>>>=20 >>>>>>>>>>> Bill >>>>>>>>>>>=20 >>>>>>>>>>> On Wed, Jan 18, 2012 at 11:18 AM, Rob = wrote: >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>> Rob wrote: >>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Very rarely(once every couple months) I have WebDNA 6.2 = stop, and drive >>>>>>>>>>>> the CPU nuts on Snow Leopard Server, and am looking at = adding a script to >>>>>>>>>>>> keep an eye on it while I go on vacation. I found an old = script... not sure >>>>>>>>>>>> where it come from or where I got it, but I had it on one = of the old >>>>>>>>>>>> servers, and would like to get it working using launchd to = start it, which >>>>>>>>>>>> isn't the problem. When I trigger the script, it comes up = with "ps: No user >>>>>>>>>>>> named 'x'". Which is fairly obvious to those who no about = these scripts, >>>>>>>>>>>> which I don't. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> So my question is, does anyone know how to get this = working, or is >>>>>>>>>>>> there a better way? ... Script below. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Rob >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> I wouldn't use that script for a couple reasons. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> First, It's not bad if your server shoots up to a 145% = usage (2 CPU's) >>>>>>>>>>>> for short instances now and then.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Second, kill -9 is *not* a good way of stopping WebDNA... = at least not >>>>>>>>>>>> for 6.2 which still uses WebDNAMonitor. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Anyway, the script seems to contain logical problems in my = opinion. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> If you were to use it, I'd change it to 199%... and change = the 'kill -9' >>>>>>>>>>>> to '/Library/WebServer/WebCatalogEngine/WebCatalogCtl = restart'. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> To fix the script, there is a change to how 'ps' functions = in Snow >>>>>>>>>>>> Leopard.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> basically change the instances of "ps -aux" in your script = to "ps aux". >>>>>>>>>>>>>=20 >>>>>>>>>>>>> To fix your CPU issue, I'd start looking into standard = troubleshooting >>>>>>>>>>>> techniques.. looking at logs, looking for overgrown log = files etc.. >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Donovan >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> Thanks for the input Donovan. >>>>>>>>>>>>=20 >>>>>>>>>>>> I'm not sure if I'm going to use it or not, at this point. = Its just an >>>>>>>>>>>> avenue I'm looking at, unless there is a better solution. I = did notice, >>>>>>>>>>>> however, that when WebDNA dies, the CPU hoovers around 60%, = so I'm not sure >>>>>>>>>>>> this will even work when it acts up. >>>>>>>>>>>>=20 >>>>>>>>>>>> I've been looking at the logs trying to pin out down, but = it happens so >>>>>>>>>>>> rarely that its hard to get a handle on it... :-( .. I = think all turn on >>>>>>>>>>>> everything in the Prefs Technical section for a while to = see if I can catch >>>>>>>>>>>> it. >>>>>>>>>>>>=20 >>>>>>>>>>>> Rob >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
christophe.billiottet@webdna.us
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:
Opposite of Summ=T? (2000)
Email within tmpl ? (1997)
Keep away (1997)
[WebDNA] OT? - how to get webdna to tell browser to open SWF directly in the browser? (2009)
Help formatting search results w/ table (1997)
Download (1999)
WebStar and CopyFile (2000)
[WriteFile] problems (1997)
Hiding Contexts (2000)
A question on sub-categories (1997)
Separate SSL Server (1997)
Date Formats (1997)
Admin Edit prob. (1997)
wierd crashes for multi-sendmails on NT (1997)
I am dumb. No see [variable] (2003)
No Access warning when caching HTML files (1997)
Size limit for tmpl editor ? (1997)
NT 4.0/IIS WebCat Installation (1998)
convert characters (2003)
WebTen? (1997)