Samba & resmgr

Anyone use Samba 2.0.7 (on any OS) in any mission critical application?

Here is why I’m asking. Current design of system I’m working on
exchanges data with Windows, implemented with TCP/IP sockets.
Works well.

But now that this system is being redesigned on NTO, some
modules are becoming resmgr. See where I’m heading…

Since Samba handles files and resmgr presents a file based
interface, a windows software can read/write into a custom
resmgr (not just the filesystem). Quick test show this work well
(have to support stat though).

Someone in management doesn’t want to rely on Samba because
he had a bad experience with Samba long time ago , when he
used to be a programmer I guess :wink:

Any negative experience anyone care to relate that would
prove management is right ;-(

\

  • Mario

Guess if nobody comments, your management was wrong :slight_smile:

Seriously though… You will find lots of experiences, good and bad, in the samba newsgroup (comp.protocols.smb). IIRC, there were threads about combining samba/appletalk and samba/nfs.

As for the qnx4 version, I built it without shared memory support (simply because qnx4 shm scheme isn’t compatible with other unix systems). So that version uses “slow file locking” methode. That might incur performance problems if you want to use it for mission critical applications.

On the other hand, in a thought experiment, it should be possible to prefix or symlink the locking directory (/usr/local/samba/var/locks) to a ramdisk, thereby speading up locking operations. Haven’t tryed, this though…

For my part, I use it just for simple Win/QNX file interchange and it works well enough for me.


regards,

rick

Previously, Mario Charest wrote in qdn.public.qnxrtp.applications:

Anyone use Samba 2.0.7 (on any OS) in any mission critical application?

Here is why I’m asking. Current design of system I’m working on
exchanges data with Windows, implemented with TCP/IP sockets.
Works well.

But now that this system is being redesigned on NTO, some
modules are becoming resmgr. See where I’m heading…

Since Samba handles files and resmgr presents a file based
interface, a windows software can read/write into a custom
resmgr (not just the filesystem). Quick test show this work well
(have to support stat though).

Someone in management doesn’t want to rely on Samba because
he had a bad experience with Samba long time ago , when he
used to be a programmer I guess > :wink:

Any negative experience anyone care to relate that would
prove management is right ;-(

\

  • Mario

    \

“Rick Lake” <rwlake@SPAM.REDIRECTED.TO.DEV.NULL> wrote in message
news:Voyager.001012220807.516111A@localhost.localdomain

Guess if nobody comments, your management was wrong > :slight_smile:

Seriously though… You will find lots of experiences, good and bad, in
the samba newsgroup (comp.protocols.smb). IIRC, there were threads about

combining samba/appletalk and samba/nfs.

Ya I guess I should look into samba newsgroup. But newsgroups usally show

people that have trouble since I don’t have any idea how many people are
using samba, it doesn’t give me a clue as to the % of success :wink:

As for the qnx4 version, I built it without shared memory support (simply
because qnx4 shm scheme isn’t compatible with other unix systems). So that

version uses “slow file locking” methode. That might incur performance
problems if you want to use it for mission critical applications.

On the other hand, in a thought experiment, it should be possible to
prefix or symlink the locking directory (/usr/local/samba/var/locks) to a

ramdisk, thereby speading up locking operations. Haven’t tryed, this
though…

For my part, I use it just for simple Win/QNX file interchange and it
works well enough for me.

For me as well, however from time to time on QNX4 it becomes unresponsive,

we have to slay
and restart it. On NTO it hasn’t enough mileage yet.

regards,

rick

Previously, Mario Charest wrote in qdn.public.qnxrtp.applications:


Anyone use Samba 2.0.7 (on any OS) in any mission critical application?

Here is why I’m asking. Current design of system I’m working on
exchanges data with Windows, implemented with TCP/IP sockets.
Works well.

But now that this system is being redesigned on NTO, some
modules are becoming resmgr. See where I’m heading…

Since Samba handles files and resmgr presents a file based
interface, a windows software can read/write into a custom
resmgr (not just the filesystem). Quick test show this work well
(have to support stat though).

Someone in management doesn’t want to rely on Samba because
he had a bad experience with Samba long time ago , when he
used to be a programmer I guess > :wink:

Any negative experience anyone care to relate that would
prove management is right ;-(

\

  • Mario


    \