Because flock() depends on operating system services that Win98 doesn't provide. Within the Windows family, you would have to upgrade to WinNT, Win2000, or WinXP to get flock().

You'll be O.K. once you move to Red Hat.

This just means you need to get a better operating system. You'll do one of a few things: alter YaBB to use native Win32 locking (not that I know how, I'm just suggesting it), move up to a Windows with POSIX capabilities (NT, Windows 2000, XP) or get a better operating operating system. You know the drill, OpenBSD, FreeBSD, NetBSD, Mac OS X, Linux, etc.

Don't be tempted to just uncomment the locking system. That's critical to preventing data corruption. Keep in mind that as long as you stick with crippled (no POSIX capabilities) operating systems like Windows 95, 98, ME your perl experience will be one frustration after another. I do the majority of my work on a Windows 2000 computer but that's augmented by a local Cygwin install and an OpenBSD server. If I had full choice of operating systems I might be using a FreeBSD desktop with Wine and/or VMWare to go windows-ish at need.

So go do something sane with your choice of new operating system.

__SIG__
use B;
printf "You are here %08x\n", unpack "L!", unpack "P4", pack
  "L!", B::svref_2object(sub{})->OUTSIDE;
[download]

What you're looking for is File::FlockDir.

Potential alternatives may be Win32::Semaphore or Win32::Mutex from http://search.cpan.org/author/GSAR/libwin32-0.191/, but I've not investigated (might be worth a look, but i'm happy with File::FlockDir's flock emulation)

Some background at File::DumbLock

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! ** The Third rule of perl club is a statement of fact: pod is sexy.

Problem is this. If you've got multiple processes with a file open for writing and reading at the same time, trouble results. So you need locking. The flock() call is one method of locking a resource in Perl.

In Win98/95, only one user is expected to be using the system at a time. Thus, file locking (at least on this level) shouldn't really be a concern, right?. The OS won't allow more than one process in Win98/95 to have a file open for writing at the same time. That solves the locking problem and makes flock() unnecessary for the OS... The problem is that Perl wants to use this locking mechanism, but it simply doesn't exist in Win98/95.

So what do you do? Well, if this were a long-term thing I'd agree with the rabble. If you're just working out the bugs, noodling around with the system before it goes into production, try this:

           # Change this
           flock(FH, LOCK_EX) || die "Error in flock: $!";

           # Into this (untested, no Win98 machine handy)
           eval { 
                flock(FH, LOCK_EX) 
                      || die "Error in flock: $!";
           };
           die unless ($@ =~ /unimplemented/);
[download]

I get the distinct impression from the question that the intention is to leave the web server on the Windows 98 machine hence my recommendation to either start using Win32 locking or get a better operating system. A basic assumption of server-side programming is that locking is of paramount importance so this isn't a problem firebird34 can dodge.

__SIG__
use B;
printf "You are here %08x\n", unpack "L!", unpack "P4", pack
  "L!", B::svref_2object(sub{})->OUTSIDE;
[download]

The server will be hosted on a Redhat flavour, but I am running on the Win98 atm, just working out any bugs that I might find and/or put in some new features. I'll try that snippit change tomorrow aswell, thanks.

I do have access to Mandrake 8.2 on my other OS, but bad e-card atm, so it's hard to transfer over.

Thanks for the help all! Didn't know that Win32 had trouble with flocking, having never used it before.