Re: Network File serving options

From: Mike Brown (mike_at_tkg.ca)
Date: 10/31/03 

Date: Fri, 31 Oct 2003 01:46:42 GMT

Justin Robbs wrote:
>
> My company has a POS system that we are updating. Currently, we have two
> Openserver machines acting as cash registers and one machine that interfaces
> to our gas pumps and our corporate office via dialup. The machines are a
> mix of 5.0.5 and 5.0.6.
>
> Right now the machines are basically stand alone in regards to the
> transaction and price files. We are want to make our gas interface machine
> a file server (it doesn't have nearly as much activity as the registers).
> Basically we want the registers to write all transaction information to the
> file server and get all pricing information off of the file server. I know
> how to do this with NFS, but I am wondering if the are some other better
> options. For example, is there something with less overhead, more
> reliability, etc, or is NFS the perfect way to go?
>

Far from perfect, but it does work on a LAN for copying files. NFS is less
suitable for sharing a database, such as a flat file system.

> Security is not a big issue. The only outside access to the system is via
> dial up and the number is not published anywhere. Also, the only access the
> user's have to our system inside the store is with a touch screen. The only
> other input devices available are the UPC scanner or credit card/check
> reader.
>
> The network is a 10mb/s network. I would like to avoid replacing the
> network hardware if possible. With only two clients, it shouldn't be very
> busy, plus none of our store layouts would allow anymore registers, save one
> that would allow 4. If that changed, it would be a new installation with
> new hardware.
>

There has been some interaction in local file systems performance when
using NFS, check back to some of Belas posts for the details.

> BTW, there will be built in fail safe measures to write locally if the
> network failed for some reason.
>

That is the most critical concept, in retail rule #1 is take the money.
The design should allow the register to run even if the network cable
is pulled.

> Any ideas, comments, or concerns, not related to porting to linux because
> "SCO sucks" would be greatly appreciated. The linux port is coming but that
> is a separate project.
>
> Thanks,
> Justin

Mike 

-- 
Michael Brown
The Kingsway Group

Relevant Pages

  • Re: Cant see FreeBSD machine in Macs Finder
    ... |>Preferences tells me that other machines on the network can access as ... You can use howl to advertise an NFS service that MacOS X will ... Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org ...
    (freebsd-questions)
  • Re: What linux lacks most - a decent remote fs
    ... openings right and it depends on uid's matching at the client and server ... What I mostly see is every imaginable problem on different machines ... to "support" NFS, but which together are highly unreliable (especially ... TCP, but if your network is a mess, it needs to be cleaned up. ...
    (Fedora)
  • Network File serving options
    ... Openserver machines acting as cash registers and one machine that interfaces ... a file server. ... The network is a 10mb/s network. ...
    (comp.unix.sco.misc)
  • Re: Help understanding error?
    ... > Running a specific program on each of the 10 machines ... I usually don't have that many machines trying to access an NFS export, ... I've also run into problems using NFS where the network infrastructure is ... I was trying to do network installs of RH9 on several ...
    (comp.os.linux.misc)
  • Re: Network File serving options
    ... > Openserver machines acting as cash registers and one machine that ... > a file server (it doesn't have nearly as much activity as the registers). ... > reliability, etc, or is NFS the perfect way to go? ... > The network is a 10mb/s network. ...
    (comp.unix.sco.misc)
Quantcast