Hello,
I have been working on this for quite some time and I can’t seem to
understand what is going on. Here is what I did:
(1) Installed Samba 2.2.4 on my QNX 6.2.0 machine from the software
repository
(2) Modified /etc/inetd.conf by adding ‘swat stream tcp nowait.400 root
/opt/sbin/swat swat -a’
(3) Modified /etc/services by adding ‘swat 901/tcp’
(4) Modified rc.local by adding -
inetd &
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
(5) Created a smb.conf file in the /opt/lib directory that reads
#Global parameters
[global]
workgroup = LOCAL
netbios name = QNX6
security = SHARE
encrypt passwords = Yes
guest account = guest
guest ok = Yes
[SAMBA]
comment = QNX Development Lib
path = /test
read only = No
(6) I did a ‘mkdir /test’ and a ‘chmod 777 /test’
(7) Rebooted my machine
When it comes back up, I did a ‘pidin’ and I found all my daemons running
(inetd, nmbd, smbd, etc…); when I rebooted again the next day, i did a
‘pidin’ and smbd and nmbd don’t come up. I can’t get those two to run now.
Even if I go into /usr/sbin and do a ‘./smbd -D’, it doesn’t run.
I don’t understand why. If you have any suggestions, I would really really
appreciate them.
Try removing the pid files. For some reason when they are killed they
are not cleaning up after themselves.
chris
Biren Mehta <bmehta7696@yahoo.com> wrote:
Hello,
I have been working on this for quite some time and I can’t seem to
understand what is going on. Here is what I did:
(1) Installed Samba 2.2.4 on my QNX 6.2.0 machine from the software
repository
(2) Modified /etc/inetd.conf by adding ‘swat stream tcp nowait.400 root
/opt/sbin/swat swat -a’
(3) Modified /etc/services by adding ‘swat 901/tcp’
(4) Modified rc.local by adding -
inetd &
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
(5) Created a smb.conf file in the /opt/lib directory that reads
#Global parameters
[global]
workgroup = LOCAL
netbios name = QNX6
security = SHARE
encrypt passwords = Yes
guest account = guest
guest ok = Yes
[SAMBA]
comment = QNX Development Lib
path = /test
read only = No
(6) I did a ‘mkdir /test’ and a ‘chmod 777 /test’
(7) Rebooted my machine
When it comes back up, I did a ‘pidin’ and I found all my daemons running
(inetd, nmbd, smbd, etc…); when I rebooted again the next day, i did a
‘pidin’ and smbd and nmbd don’t come up. I can’t get those two to run now.
Even if I go into /usr/sbin and do a ‘./smbd -D’, it doesn’t run.
I don’t understand why. If you have any suggestions, I would really really
appreciate them.
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Hello,
If by the pid files, you mean the files in the /proc directory, I tried that
and had no luck.
If you have any other suggestions, that would be great.
Thanks,
Biren
“Chris McKillop” <cdm@qnx.com> wrote in message
news:b45hgh$mm8$1@nntp.qnx.com…
Try removing the pid files. For some reason when they are killed they
are not cleaning up after themselves.
chris
Biren Mehta <> bmehta7696@yahoo.com> > wrote:
Hello,
I have been working on this for quite some time and I can’t seem to
understand what is going on. Here is what I did:
(1) Installed Samba 2.2.4 on my QNX 6.2.0 machine from the software
repository
(2) Modified /etc/inetd.conf by adding ‘swat stream tcp nowait.400 root
/opt/sbin/swat swat -a’
(3) Modified /etc/services by adding ‘swat 901/tcp’
(4) Modified rc.local by adding -
inetd &
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
(5) Created a smb.conf file in the /opt/lib directory that reads
#Global parameters
[global]
workgroup = LOCAL
netbios name = QNX6
security = SHARE
encrypt passwords = Yes
guest account = guest
guest ok = Yes
[SAMBA]
comment = QNX Development Lib
path = /test
read only = No
(6) I did a ‘mkdir /test’ and a ‘chmod 777 /test’
(7) Rebooted my machine
When it comes back up, I did a ‘pidin’ and I found all my daemons
running
(inetd, nmbd, smbd, etc…); when I rebooted again the next day, i did
a
‘pidin’ and smbd and nmbd don’t come up. I can’t get those two to run
now.
Even if I go into /usr/sbin and do a ‘./smbd -D’, it doesn’t run.
I don’t understand why. If you have any suggestions, I would really
really
appreciate them.
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Biren Mehta <bmehta7696@yahoo.com> wrote:
Hello,
If by the pid files, you mean the files in the /proc directory, I tried that
and had no luck.
If you have any other suggestions, that would be great.
No, I belive it puts files in /opt/var somewhere. The servers writes them
out to track if a copy is already running.
chris
\
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/