> many ways to solve the problem. Amongst the real issues that
> the person will ultimately need to work out is whether it is
> really SANE to be writing temp files to begin with I mean
Yes! That is the other thing. If you write a script that writes temp
files you should consider it LOCAL ON
On Wednesday, Sep 17, 2003, at 18:02 US/Pacific, Dan Anderson wrote:
[..]
It is possible to use .htaccess files, apache config directives, and
burying 777 directories in 700 directories to add to the security of
having a 777 directory.
dan,
my complements! on the XML.document - and yes, there ar
> less acceptable on more and more web-sites. Prudence
> generally dictates 755 where other members of your group
> and the rest of the world can read and execute.
It is possible to use .htaccess files, apache config directives, and
burying 777 directories in 700 directories to add to the securi
On Wednesday, Sep 17, 2003, at 14:15 US/Pacific, John Park wrote:
[..]
Although I don't understand why I can't write to the same directory
my CGI scripts are located in. I've done this before on Free Webhosts
like tripod and netfirms.
[..]
while we are all deeply and emotionally committed
to our
On Wednesday, Sep 17, 2003, at 18:50 US/Pacific, ram Osuri wrote:
I agree with your assesment .. to solve this problem you might want to
do a
chmod 777 newfile.txt and then run the program it will work then
Actually there are two problems with this.
a. there is no reason to set the execute bits
On Wednesday, September 17, 2003, at 03:56 PM, drieux wrote:
Remember that most web servers are running as the
web-server uid - www or apache - and so can only 'write'
where that uid has 'write permission'. It can of course
read/execute anything that is 'world readable/executable'
but as a genera
On Wednesday, Sep 17, 2003, at 11:59 US/Pacific, John Park wrote:
[..]
This is what my script looks like:
#!/usr/bin/perl
use CGI;
...
...
open(FILE,">newfile.txt") || die("newfile.txt: $!"); #script stops
here due to permissions
[..]
that is the correct syntax - although you might
not want to '
John,
I may be a little old fashioned, however, the code below seems to work
OK.
>open(INFILE, "@info = ;
>close(INFILE);
Sincerely in Christ,
Mark-Nathaniel Weisman
President / Owner
Outland Domain Group Consulting
Anchorage / Washington DC / Bellevue
[EMAIL PROTECTED]
-Original Message
