Has anyone managed to install and use Samba on QRTP ?
I have downloaded and installed the samba-2.0.7-nto.tgz port of samba
for RTP. This file is available under the “contributed software” site
at QDN. The whole installation seems to perform as instructed. I can
even run the swat utility from a remote system to setup the Samba
configuration.
The problem I am having is that whenever you try to start the “smbd”
daemon it results in
“Memory Fault (core dumped)”. I am trying to start it manually with
smbd -D and also trying it with inetd starting it. I initially thought
that the binary was corrupted but if I do a smbd -V or -h it will return
the version or usage correctly. Any other command line parameters cause
a memory fault.
The only other strange observation is that the swat configuration (html)
page for setting the globals has about 3-4 lines full of garbage just
below the box to enter the netbios name. At one point it even wrote all
this garbage into the smb.conf file. If I edit the smb.conf file and
remove the garbage from the file, it still appears in the HTML interface
to swat.
Has anyone else seen or heard of any of these problems before ?
Samba just won’t samba.
Previously, FibreBoy wrote in qdn.public.qnxrtp.devtools:
Has anyone managed to install and use Samba on QRTP ?
I have downloaded and installed the samba-2.0.7-nto.tgz port of samba
for RTP. This file is available under the “contributed software” site
at QDN. The whole installation seems to perform as instructed. I can
even run the swat utility from a remote system to setup the Samba
configuration.
The problem I am having is that whenever you try to start the “smbd”
daemon it results in
“Memory Fault (core dumped)”. I am trying to start it manually with
smbd -D and also trying it with inetd starting it. I initially thought
that the binary was corrupted but if I do a smbd -V or -h it will return
the version or usage correctly. Any other command line parameters cause
a memory fault.
The only other strange observation is that the swat configuration (html)
page for setting the globals has about 3-4 lines full of garbage just
below the box to enter the netbios name. At one point it even wrote all
this garbage into the smb.conf file. If I edit the smb.conf file and
remove the garbage from the file, it still appears in the HTML interface
to swat.
Has anyone else seen or heard of any of these problems before ?
Samba just won’t samba.
If the executable was built for the original RTP release, then Samba
may be suffering from the same problems that emacs had: the
executable for the first release would not run on the Patch A kernel.
It just crashed on startup. The solution was to re-link (didn’t even
have to recompile source), and everything was fine. You may be
looking at building Samba from source, unless somebody has a working
version around. Have you tried the Samba archive on www.qnxstart.com?
It might be better.
Cheers,
Andrew
Andrew,
The documentation with the version of Samba I am using says it is for NTO 2.11
QRTP
and I am using the version of nuetrino that was available on Jan. 18, 2001
I am at a complete loss of how or what denotes a version of QNX whether it is
a version number of nuetrino or as you say “Patch A kernel” RTP or QNX6. I
have found no way to tell what version of anything is even running on my
system. I just run the package manager and hope that every thing is the
latest.
Now how does the Patch A kernel relate with Nuetrino 2.11 ?
I am downloading the samba file from qnxstart.com as I am writing this but it
appears to be the exact same file I downloaded from the qdn contributed
software.
Thanks,
FibreBoy
Andrew Thomas wrote:
If the executable was built for the original RTP release, then Samba
may be suffering from the same problems that emacs had: the
executable for the first release would not run on the Patch A kernel.
It just crashed on startup. The solution was to re-link (didn’t even
have to recompile source), and everything was fine. You may be
looking at building Samba from source, unless somebody has a working
version around. Have you tried the Samba archive on > www.qnxstart.com> ?
It might be better.
Cheers,
Andrew
FibreBoy a écrit :
Andrew,
The documentation with the version of Samba I am using says it is for NTO 2.11
QRTP
and I am using the version of nuetrino that was available on Jan. 18, 2001
I am at a complete loss of how or what denotes a version of QNX whether it is
a version number of nuetrino or as you say “Patch A kernel” RTP or QNX6. I
have found no way to tell what version of anything is even running on my
system. I just run the package manager and hope that every thing is the
latest.
Now how does the Patch A kernel relate with Nuetrino 2.11 ?
I am downloading the samba file from qnxstart.com as I am writing this but it
appears to be the exact same file I downloaded from the qdn contributed
software.
Thanks,
FibreBoy
Andrew Thomas wrote:
If the executable was built for the original RTP release, then Samba
may be suffering from the same problems that emacs had: the
executable for the first release would not run on the Patch A kernel.
It just crashed on startup. The solution was to re-link (didn’t even
have to recompile source), and everything was fine. You may be
looking at building Samba from source, unless somebody has a working
version around. Have you tried the Samba archive on > www.qnxstart.com> ?
It might be better.
Cheers,
Andrew
I don’t really believe in a problem with some version of qrtp. I use Samba for a
long time, I’am working now with patch A
and everything is fine (allmost because we are wondering about all the threads
created but it works well).
I think that lot of people have downloaded this package yet. It should be ok.
I didn’t experiment such problems.
What I can say is that you need the full tcp-ip stack and not the tiny tcpip
started by default.
I didn’t verify with the last qrtp release but normally io-net is started with
-pttcpip (note the double ‘t’).
This is a snippet of my rc.local file:
rm -f /usr/local/samba/var/locks/nmbd.pid # when the system or samba crash these
files still exists
rm -f /usr/local/samba/var/locks/smbd.pid
slay io-net
/sbin/io-net -del900 -ptcpip # el900 for my 3C905 ethernet card
echo “wait for socket”
waitfor /dev/socket 30
if test -d /dev/socket; then
echo “configure full tcp/ip stack”
/usr/bin/ifconfig en0 aaa.bbb.ccc.ddd # insert your ip address here
/usr/bin/route add default eee.fff.ggg.hhh #not necessary
echo “mount qnet”
mount -T io-net /lib/dll/npm-qnet.so # you can aslo start qnet with io-net with
-pqnet
echo “start inetd”
inetd
echo “start samba”
/usr/local/samba/bin/nmbd -D
/usr/local/samba/bin/smbd -D
echo “mount a windows share”
/usr/sbin/fs-cifs //netbio_name:its.ip.address.zzz:/share /mnt/local_name login
passwd
else
echo “/dev/socket not mounted”
fi
Alain.
I have also experienced a problem when starting SMBD. The problem was that
SMBD couldn’t find the IPaddress of the host where SMBD was started.
I fixed this by adding an entry for my host in the /etc/hosts file.
After that SMBD could start. To enable QNX to at all read the /etc/hosts
file
I think that the line ‘lookup file bin’ must exist first in the
/etc/resolve.conf file.
regards
/MP
“FibreBoy” <fibreboy777@hotmail.com> wrote in message
news:3A919DB5.E44685E7@hotmail.com…
Has anyone managed to install and use Samba on QRTP ?
I have downloaded and installed the samba-2.0.7-nto.tgz port of samba
for RTP. This file is available under the “contributed software” site
at QDN. The whole installation seems to perform as instructed. I can
even run the swat utility from a remote system to setup the Samba
configuration.
The problem I am having is that whenever you try to start the “smbd”
daemon it results in
“Memory Fault (core dumped)”. I am trying to start it manually with
smbd -D and also trying it with inetd starting it. I initially thought
that the binary was corrupted but if I do a smbd -V or -h it will return
the version or usage correctly. Any other command line parameters cause
a memory fault.
The only other strange observation is that the swat configuration (html)
page for setting the globals has about 3-4 lines full of garbage just
below the box to enter the netbios name. At one point it even wrote all
this garbage into the smb.conf file. If I edit the smb.conf file and
remove the garbage from the file, it still appears in the HTML interface
to swat.
Has anyone else seen or heard of any of these problems before ?
Samba just won’t samba.
Thanks for all the help from everyone. I have finally managed to get Samba
running correctly on a system at home with my local LAN. I think the trick
was the rc.local and etc/hosts files. The original problem began on a system
at work that I originally installed the Samba image for QNX4 on a Nuetrino
system. Once I realized this I uninstalled it and re-installed the NTO
version. This may be causing some lingering after effects. Once I went home
and started fresh using the correct binaries I finally managed to get it
working.
Thanks again,
FibreBoy
Mats Pettersson wrote:
I have also experienced a problem when starting SMBD. The problem was that
SMBD couldn’t find the IPaddress of the host where SMBD was started.
I fixed this by adding an entry for my host in the /etc/hosts file.
After that SMBD could start. To enable QNX to at all read the /etc/hosts
file
I think that the line ‘lookup file bin’ must exist first in the
/etc/resolve.conf file.
regards
/MP
“FibreBoy” <> fibreboy777@hotmail.com> > wrote in message
news:> 3A919DB5.E44685E7@hotmail.com> …
Has anyone managed to install and use Samba on QRTP ?
I have downloaded and installed the samba-2.0.7-nto.tgz port of samba
for RTP. This file is available under the “contributed software” site
at QDN. The whole installation seems to perform as instructed. I can
even run the swat utility from a remote system to setup the Samba
configuration.
The problem I am having is that whenever you try to start the “smbd”
daemon it results in
“Memory Fault (core dumped)”. I am trying to start it manually with
smbd -D and also trying it with inetd starting it. I initially thought
that the binary was corrupted but if I do a smbd -V or -h it will return
the version or usage correctly. Any other command line parameters cause
a memory fault.
The only other strange observation is that the swat configuration (html)
page for setting the globals has about 3-4 lines full of garbage just
below the box to enter the netbios name. At one point it even wrote all
this garbage into the smb.conf file. If I edit the smb.conf file and
remove the garbage from the file, it still appears in the HTML interface
to swat.
Has anyone else seen or heard of any of these problems before ?
Samba just won’t samba.