• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

rc5 remote buffer syntax

JC

Diamond Member
Can't seem to get the syntax right for 'remote buffer directory'.......keep getting 'remote buffers currently not available', which I suppose means I don't have the path right. What's the correct path syntax here?

thanks.
 
Boy, what a flashback. I haven't run RC5 for a long time (back when a Cely300A@450 was hot stuff 😉 ), which means I can't remember the exact syntax. Sorry. Bump for you though.

What I do remember (and it may have changed) was that using the remote buffers (storing wus on a networked folder) was problematic and running PProxy took care of things.

Hopefully someone will come along who uses RC5 and help out.

🙂

oh, and it might help troubleshoot if you posted the path syntax you are currently using. 🙂
 
Ray is completely right on this. Remote buffers are totally not the way to go.

If two machines happen to go for a block at the same time (happens more often than you think it would) you wind up with a record lock and no machine can access the buffer file any more. The only way to unlock the buffer file is to re-boot the machine.

A personal proxy is very easy to set up and uses FIFO (first in, first out) to keep your blocks nice and fresh. I used to run one out at work with 10 machines fetching/flushing and never had a hickup on an old Gateway P5-133 non MMX. It also served as an in-house Apache server.

Give it a try!
 
Back
Top