Previously, Johan Siegers wrote in qdn.public.qnxrtp.newuser:
Cowboy pointed me to a samba in qpr form
Installation itself was not a problem, but to configure and to run it ?
I adapted the /etc/inetd.conf file so that it uses smbd and nmbd from
Well, I start them from rc.local but that should be of no consequence.
The files here are of feb 8th.
I copied the smb.conf file over to /opt/etc
Didn’t know ( or don’t remember ) that one was supplied ?
Adapted mine from a linux samba server known to work.
I run /bin/testparm and this gave no errors now.
Uh, that doesn’t necessarily mean that everything is right,
it just means that there is nothing =wrong= with the file as
it presently is ( it can be parsed, the syntax is correct ) but
it does not mean that it’s a proper config file with correct
user permissioning, security, etc.
Yet my QNX computer can not be found by a windows computer.
If nmbd is running, and it’s configured correctly, it should
be able to be found in its workgroup.
Worst case, it should be found by IP directly.
With the old version that I compiled/installed myself I could see the
computer and its shares.
If you used the same config, you’re very close.
What else do I have to configure ?
Sadly, this may well depend on which version(s) and which incantations
of which patch-levels of which windows the clients are !
Anything pre-win2K and NOT winMe should work with basic stuff.
This version does have the Win2K stuff in it, which will break pre-win2K
versions of NT, and some Win9x based systems if configured incorrectly.
The qpr also includes ( thankfully ) and installs SWAT, the web-browser
based SAMBA administration tool.
Add a line ( if you haven’t already ) in /etc/inetd.conf that looks like this :
swat stream tcp nowait root /usr/sbin/swat swat
and add one in /etc/services that looks like this :
swat 901/tcp # Enable swat management of SAMBA
Because I’m so new with qnxrtp, I’ld re-boot, though I’m sure that if you
know what order in which to terminate and re-start what, it’s completely
Bring up Voyager, and address http://127.0.0.1:901
You should get a log-in box asking for username and password.
Root can administer, most any other user can only view some parameters.
This should at this point give you a web-page based administration and
documentation tool, complete with how-to’s and about everything you
For me, it’s working great so far. Sadly, I’m on a road-trip, and it
may be a week or three before I get back to my test beds, and see if it
does what I REALLY want it to do…
Hope this helps…
My mother was a test tube; my father was a knife.