Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1) When you run samba under inetd, samba has to be loaded everytime inetd hands off a connection. Tons of overhead using this method. When it runs as a stand alone daemon, it never unloads itself. 2) Gremlins. Probably from the last solar eclipse, no wait! From the last solar flare. Cover the server in tin foil and it should fix the problem. ( Note: More details are needed before any diagnostic attempts are made ) Judy Lin wrote:>Hello. > I know that it is recommended to run smbd as a standalone daemon and to >avoid inetd. Can you please tell me why inetd is discouraged and what >problems it imposes? > >Also, I have one user who is having problems accessing her personal files >on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? > >Judy Lin >NACS-DCS > >- -- Sean Kennedy PGP public key: http://tpno.org/keys/0xFC1C377F.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1-nr1 (Windows 2000) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE//vskIjyA6vwcN38RAg4KAJwKuLHGdQEEJGbU158FDnjxG7RUJwCeP7ZL lenX5r5V9/mu9uFPMyssNt8=HvNb -----END PGP SIGNATURE-----
It turns out that the home directory name was too long (under smb.conf [Username too Long]) and shortening it fixed the save problems. I did not know there was a character limit. The user's permissions were all correct. Seems with MacOSX 10.3.2, there are problems saving files after it has been edited on the samba share. It will error out and say "operation can not be completed because one or more items are missing -47". When you click on cancel, it will create a file named in an incomprehensible way. Any ideas? Judy Lin NACS-DCS On Fri, 9 Jan 2004, Craig White wrote:> On Fri, 2004-01-09 at 11:34, Judy Lin wrote: > > Also, I have one user who is having problems accessing her personal files > > on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? > -- > guessing...permissions. Not a member of the group that is permitted to > access or different level of group member - not the primary group but a > secondary group and samba is dealing with secondary groups very well. > > The solution is typically the logs...RHL > /var/log/samba/log.username_or_ip-address would probably tell you why. > > Craig >