Re: [SLE] smbd keeps dying - HELP

From: Dan Weisenstein (dan_at_tesoro.com)
Date: 06/08/04

  • Next message: John Coldrick: "Re: [SLE] Graphics Cards for 9.0, 9.1??" 
    Date: Tue, 08 Jun 2004 13:54:33 -0700
To: suse-linux-e@suse.com

    The shared directory is set to 777 and the directory underneath that
    holds the Access tables is set to 777. All of the tables are set to 666.
    The shared file system is mounted with options acl,user_xattr. Each user
    has an account on the server, and the smbpasswd set for each user. The
    file system is mapped to Y: on each XP users machine. Files can be
    created, modified, etc.

    I don't think setting the sticky bit would do anything. The database
    lock file gets set to 644 (or 666) depending on the Samba 'create mask'
    attribute. If set to 644, the lock file is set to 644 and the owner is
    set to the person who created it. This results in an error for all other
    users that the database is "locked" by another user. If the lock file is
    set to 666, this results any second+ attempts to access the tables
    getting hung, which then hangs everything.

    Since I've observed Access in action on a XP Server, and there is only
    one lock file created per table no matter how many users are accessing
    the table, I have to assume that the lock file must be active to all
    users, and not exclusively "owned" by the creator. The databases are set
    up for row locking vs. table locking, to facilitate multiple user access.

    The key seems to be access to the table lock being somehow shared by
    multiple users. Surely having Access tables on a linux server isn't new.
    Anybody else have any ideas?

    Thanks- Dan

    James Golden wrote:

    >One thing I do know about access is it is hard to configure for multiple
    >users. I would check your permissions for the directory. Users have to
    >be able to read/write/create to the directory. You may change that on
    >the access file if you want to restrict some people but they have to
    >have full permissions in the directory.
    >
    >In samba you can put a "sticky bit". There is an option to set
    >permissions for new files. The permission on this or on the directory
    >for the files will have to be 777.
    >
    >That should work for you.
    >
    >Sincerely,
    >James Golden
    >
    >On Tue, 2004-06-08 at 12:25 -0700, Dan Weisenstein wrote:
    >
    >
    >>Hello,
    >>
    >>I have a 9.1 server set up with one Samba share. On this share are the
    >>database tables for several MS Access databases. As long as only one
    >>WindowsXP system accesses the tables, all is well. As soon as another
    >>one tries access, everything Samba Server related hangs. NFS also hangs.
    >>One or more smbd's die and nothing short of a reboot frees things up.
    >>/etc/init.d/smb stop fails. cd'ing into the shared drive hangs the
    >>terminal window.
    >>
    >>When an MS Access client opens one or more tables, a lock file gets
    >>created called databasename.ldb. I had the Samba create permissions set
    >>to 0644, but that locks out everybody else out of the tables. If I
    >>change the create perms on the Samba share to 0666, the lock file is
    >>created with 666 perms, but another Access instance hangs everything and
    >>the dead smb processes appear. When this was a Windows server, I had no
    >>problems with several people accessing the tables at the same time; as
    >>it's supposed to be.
    >>
    >>The current Samba Server version is 3.04 I believe. I even tried
    >>removing Samba and re-installing 3.02a (which is on the 9.1 CD's), but
    >>no difference. Can anyone please help?
    >>
    >>Thanks- Dan
    >>
    >>
    >>--
    >>Check the headers for your unsubscription address
    >>For additional commands send e-mail to suse-linux-e-help@suse.com
    >>Also check the archives at http://lists.suse.com
    >>Please read the FAQs: suse-linux-e-faq@suse.com
    >>
    >>y
    >>
    >>
    >
    >
    >
    >

  • Next message: John Coldrick: "Re: [SLE] Graphics Cards for 9.0, 9.1??"

    Relevant Pages

    • Re: Cant open websites from Front Page
      ... I assume you're opening a site on a remote server. ... But they gave me no option to 'delete' the lock file. ... somehow gotten corrupted. ... how FP security and NTFS security combine to give the effective rights. ...
      (microsoft.public.frontpage.extensions.windowsnt)
    • Re: [SLE] smbd keeps dying - HELP
      ... I would check your permissions for the directory. ... In samba you can put a "sticky bit". ... everything Samba Server related hangs. ... > change the create perms on the Samba share to 0666, the lock file is ...
      (SuSE)
    • Re: [SLE] smbd keeps dying - HELP
      ... > I have a 9.1 server set up with one Samba share. ... everything Samba Server related hangs. ... > change the create perms on the Samba share to 0666, the lock file is ...
      (SuSE)
    • Re: Cant open websites from Front Page
      ... I assume you're opening a site on a remote server. ... But they gave me no option to 'delete' the lock file. ... There are reports that FP extensions are not in place for this ... how FP security and NTFS security combine to give the effective rights. ...
      (microsoft.public.frontpage.extensions.windowsnt)
    • Re: POP3, lock files and procmail
      ... >> POP3 clients out there for all platforms, and the server I'm using is ... The only situation I can think of where the lock file should be ... prevent the spool from being altered while transferring which ...
      (comp.os.linux.networking)
    Loading