yitzle wrote:
> I got a CGI script that is being used by multiple users.
> It reads/writes data to a database (text file).
> When it reads, it reads the entire file, and when it writes, it
> tuncrates and rewrites the entire file.
> Can/will this screw up the file if two people try to write to the
On Sun, April 22, 2007 12:52 am, yitzle wrote:
> I got a CGI script that is being used by multiple users.
> It reads/writes data to a database (text file).
> When it reads, it reads the entire file, and when it writes, it
> tuncrates and rewrites the entire file.
> Can/will this screw up the file i
I got a CGI script that is being used by multiple users.
It reads/writes data to a database (text file).
When it reads, it reads the entire file, and when it writes, it
tuncrates and rewrites the entire file.
Can/will this screw up the file if two people try to write to the file
at the same time?
"Chas Owens" schreef:
> Dr.Ruud:
>> Chas Owens:
>>> But Synopsis 4* says
>>>There is no foreach statement any more. It's always spelled
>>> for in Perl 6,
>>>so it always takes a list as an argument
>>
>> Well Perl6 isn't Perl, it's a successor to Perl. Like Perl did, Perl6
>> took
On 4/21/07, Dr.Ruud <[EMAIL PROTECTED]> wrote:
"Chas Owens" schreef:
> But Synopsis 4* says
>There is no foreach statement any more. It's always spelled for
> in Perl 6,
>so it always takes a list as an argument
Well Perl6 isn't Perl, it's a successor to Perl. Like Perl did, Per
"Chas Owens" schreef:
> But Synopsis 4* says
>There is no foreach statement any more. It's always spelled for
> in Perl 6,
>so it always takes a list as an argument
Well Perl6 isn't Perl, it's a successor to Perl. Like Perl did, Perl6
took a lot of good parts out of other language
On 04/20/2007 07:29 PM, John Maverick wrote:
Folks,
Got a question regarding perl code in cgi script.
I am running below line of code in cgi script which doesn't work as
expected.
my $ticket = qx{echo $p4pass | p4 login -p $p4user};
Basically command has to return a ticket or error message. I
