IW Samba and Solaris Samba?

A question/confirmation about the version of Samba that is included within the TeamSite 5.5.2 (Solaris) bundle-

other than the name of a few configuration files and the location of the application itself, there isn't anything fundamentally different with the version of Samba included in the TeamSite bundle than with a typical version of Samba that would be installed off of the OS, correct? They are basically the same product, whether you extract and download from the TeamSite bundle, or install seperately as part of the Solaris install / setup, aren't they? there isn't any proprietary differences to be aware of in the TeamSite bundled version, is there?

The reason I ask is due to the fact that a sysadmin resource on the project who, because the /samba folder is installed under /iw-home and came from the TeamSite distribution, feels that any samba-related setup and/or issues are TeamSite-specific issues to be raised with IW support, and thus do not necessarily fall within the domain of a "OS-level only" sysadmin-

I want to make sure that when I tell him that Interwoven's version of Samba (iw-home/samba/....), and Solaris' version of Samba (usr/local/samba/...) are equivalents in terms of setup, use, maintenance, etc, that this is correct?

I'm basing this judgment on experience that you can use the OS Samba copy of Samba instead of TeamSite copy of Samba to enable filesharing- but perhaps there's limitations to doing this that I've overlooked in the past?

thanks for all replies

Find more posts tagged with

Comments

Migrateduser

When I asked technical support this same question they told me they were the same, that Samba was just bundled to normalize the version and simplify installation. In fact I think the book says that you need not install Samba if you already have it running. Just a second let me see if I can find that ...yeah, pg 41 of the V5.0 Administration Guide offers the typical configuration file locations if Samba is already installed before TeamSite.

gsumers22texas

thanks for confirming the info tgt_usa-

does anybody know any application ramifications if we disable the iw-home/samba instance of samba installed with TeamSite, and configure/use/enable the OS's /usr/local/samba instance of samba instead?

in other words, is /iw-home/samba only used for filesharing, or is it also used for any other functions within the app itself?

thanks for all replies-

Adam Stoller

It is only used for file sharing - I'm 99% sure since you can have TeamSite running without Samba at all if you don't wish to share the IWSERVER mount points.

--fish
(Interwoven, Curriculum Development)

Migrateduser

This is correct. You do not need Samba running at all unless you want to give filesystem access directly to the local windows users (unix users would use the nfs share created by TeamSite.. the same one used for /iwmnt and /.iwmnt).

If you don't want to give any of your users access to the virtual filesystem directly, then samba is not needed at all (and NFS is only needed locally).

gsumers22texas

excellent- many thanks for confirmation-
99% and "do not need at all" certainty beats my 92% certainty every day Smiley Embarassed

)

gsumers22texas

Another "what depends on IW samba" question that I'd like a "second set of eyes" confirmation upon:

earlier I asked about TeamSite's use of Samba, and identified it's only used for file sharing-

but what about Front Office (TFO) 5.5.2?

I assume that the "mapped network drive" TFO client users will require it (but we won't have any of these), but what about the TFO client "briefcase" users? I don't see Samba in the architecture diagram (it indicates SOAP instead) nor is "samba" or "iw.smb.conf" mentioned in the Admin doc at all (not even in "mapped network drive" user discusssions? does this rely on SOAP now also?)