This is a three part question.
1. ====================
With the upgrade to 18p4, samba is regularly causing our server to run
out of processes.
What is causing this? It never happened w/ 17p2.
OS: IRIX 6.2
log.smb has the following:
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
04/25/1998 16:30:30 Connection denied from 206.197.67.130
04/25/1998 16:30:30 Connection denied from 206.197.67.130
04/25/1998 16:30:33 Connection denied from 206.197.67.107
04/25/1998 16:30:33 Connection denied from 206.197.67.107
04/25/1998 16:30:44 Connection denied from 206.197.67.107
04/25/1998 16:30:44 Connection denied from 206.197.67.107
04/25/1998 16:30:45 Connection denied from 206.197.67.130
04/25/1998 16:30:45 Connection denied from 206.197.67.130
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
ERROR: Recursion in sig_cld? Perhaps you need `#define USE_WAITPID'?
Is this the fix? Use USE_WAITPID and compile again? What other impact
would that have?
2. =========================
Also, we have a NT server on the network. It is the domain master for
a domain called NTDOMAIN. The Samba server is set up for the domain
WORKGROUP and NOT the domain master.
All the users log on to the NTDOMAIN from their NT Workstation and mount
drives from the Samba server. That should be fine, right?
We tried to set Samba to belong to the NTDOMAIN, but that seemed to
have triggered the above "out of processes" problem. (could be
unrelated).
3. ==========================
When USER1 logs on to a client machine CLIENT1 and mounts \\samba\homes
to drive F:. USER1 logs out.
USER2 logs on. She is not asked for the password for F:, but she cannot
access it either. Unmounting F: and mounting it again as \\samba\homes
works again.
This was not the behavior in 17p2
We are using security=SHARE and non-encrypted passwords.
What are we doing wrong?
===================Thanks for any help!!
-vince
