If you mean "at file creation-time" with "at the same time", set the umask of the executing user to your liking.

otherwise, if modifying the permissions after file-creation is sufficient, have a look at chmod

chmod 0666, $filepath;
[download]

Hi, This place is great. Thanks for the prompt replies.

So my code becomes:

open (FILEHANDLE, ">>$filepath")||&ErrorMessage;
print FILEHANDLE "$pageoutput";
close FILEHANDLE;
chmod 0666, $filepath;

Intuitively I think that is what I would have guessed but I was hoping someone would suggest a way of ammending my code in a way that included permissions in the open filehandle line.

thanks again.

Best wishes

Sid

Intuitively I think that is what I would have guessed but I was hoping someone would suggest a way of ammending my code in a way that included permissions in the open filehandle line.

Then, like the other poster suggested, play with umask. On my system, its default value is 2, creating plain files with permissions 0664. If you were to (temporarily) set it to 0, the file created should have permissions set to 0666. It does for me.

my $umask = umask 0;
open (FILEHANDLE, ">>$filepath")||&ErrorMessage;
umask $umask;
print FILEHANDLE "$pageoutput";
close FILEHANDLE;
[download]

if you're on a *nix platform, check out umask.

You can also use umask from Perl. perldoc -f umask

if you're on a *nix

Correction, if you're using perl, given you consult perlport and perl$youros

See also perldoc -f sysopen, or perldoc POSIX then search for open.

Hi,

So is this the correct syntax for sysopen to do the following. If filepath does not exist create a file with the name contained in the filepath with permissions 666, print some stuff to the file and then close it?

sysopen (FILEHANDLE, ">>$filepath",O_CREAT, 0666)||&ErrorMessage;
print FILEHANDLE "$pageoutput";
close FILEHANDLE;

Thanks

Sid

A couple of points:
1) chmod and the sysopen* call above set the file mode not the permission
2) A file mode of 0666 is generally bad as it is generally allows more access to the file than is needed (do you really want everyone to be able to read/change/delete your file?)
3) If you need to modify owner or the group membership, use chown

CC

Updated: Ok, you can't actually delete the file unless you have write access to the directory whihch holds the file. You can, however, blank out the file. For example:

> my.file
[download]

will reduce the file to zero bytes without actually having write access to the directory. The file isn't deleted but it certainly isn't very useful now.

* if your umask is sane (ie 022) then the sysopen (FILEHANDLE, ">>$filepath",O_CREAT, 0666) will not be inherently insecure.

What happens when you try it?

(And you probably should also read perldoc perlopentut which gives examples of correct use of sysopen().)