The following reply was made to PR mod_include/2783; it has been noted by GNATS.
From: dannyman <[EMAIL PROTECTED]> To: Marc Slemko <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: mod_include/2783: #exec directive non-functional, other directives fine Date: Wed, 5 Aug 1998 09:34:14 -0500 On Tue, Aug 04, 1998 at 09:12:18PM -0700, Marc Slemko wrote: > On 5 Aug 1998, Dan Howard wrote: > > > <link rev="made" href="mailto:[EMAIL PROTECTED]"> </head><body > > text="#000000" link="#3333ff" vlink="#990000" bgcolor="<!--#exec > > cmd=".bin/randcolor" -->"> > > > > <!--#exec cmd="/bin/date" --> > > Erm... are the above two things really the exact things you are trying to > use? > > Neither are valid; ".bin" doesn't make much sense, and the second one > shouldn't have the new line before the -->. Yes they are. The first one makes perfect sense, because <cwd>/.bin is the directory from which I'm executing randcolor. It works on another host. The newline I popped in there just to test the rule of having whitespace before the end comment. With or without the newline though, the server parses that string, and leaves nothing in its place. I'd guess maybe there's a bug in capturing the stdout of the exec? (Yes, though, I popped /bin/date in there to test an absolute pathname just in case the directory environment had changed for #exec.) Have you any suggestions for an #exec that should without question work? :) I'll try setting up 1.3 on my workstation here when I have some spare time, and see if there's any difference. -dan -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC)
