lkml.org 
[lkml]   [1999]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: NFS locking
    Date
    From
    > Hi!
    >
    > NFS locking does not seem to work with Linux clients and Solaris
    > server. The fcntl locking request returns ENOLCK and in the kernel log
    > the following lines are printed:
    >
    > Dec 7 15:58:27 bcica kernel: nsm_mon_unmon: rpc failed, status=-13
    > Dec 7 15:58:27 bcica kernel: lockd: failed to monitor 164.48.158.2
    >
    > Locking does work on Solaris clients, with the same server.
    >
    > Should this work or not?

    It should (and does, I just verified it last week, Solaris 2.6 server).

    Likely you are missing statd on either or both machines. I'm guessing
    that it's missing on the Solaris box as Sun's statd could be used to
    exploit certain "features" of the automounter to gain root access unless
    it was run as a user other than root. Recently, Sun released a patch
    to fix this, however now statd will not start unless it is started by
    root... Another possibility is a paranoid admin. Use rpcinfo to verify
    that you can talk to statd and lockd on the server (and that the server
    can talk to statd and lockd on your box).

    /Anders

    --
    -- Of course I'm crazy, but that doesn't mean I'm wrong.
    Anders Hammarquist | iko@cd.chalmers.se
    Physics student | Hem: +46 31 47 69 27
    Chalmers University of Technology, G|teborg, Sweden | Mob: +46 707 27 86 87



    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:55    [W:0.024 / U:118.172 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site