Re: Cannot start ksh on HP-UX 11.11 C3600 after installation of patches

From: Florian Anwander (spam.interessiert.nicht_at_mnet-online.de)
Date: 09/29/05

  • Next message: Arkadiy: "Re: availability of "typeof" keyword" 
    Date: Thu, 29 Sep 2005 10:06:05 +0200

    Hi Marty

    > Florian Anwander wrote:
    > : If NFS try:
    > : rm $HOME/.sh_history
    > : ln /tmp/bla $HOME/.sh_history
    >
    > How will this help? You won't be able to do a hardlink if one was NFS.
    > If a symlink, won't the lock still have problems? Or does it follow
    > the symlink to the local FS before trying to lock?
    Of course you are right! It should have been a symlink. And yes: first
    the link is followed and then the lock is done.

    Florian

  • Next message: Arkadiy: "Re: availability of "typeof" keyword"

    Relevant Pages

    • Re: flock, fcntl, lockf?
      ... remove the lock), the lock disappears. ... I also use symlink locking, which is also NFS safe, mainly in my shell ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: Cannot start ksh on HP-UX 11.11 C3600 after installation of patches
      ... You won't be able to do a hardlink if one was NFS. ... the symlink to the local FS before trying to lock? ...
      (comp.sys.hp.hpux)
    • Re: googleearth complains about file instance-running-lock
      ... Unable to create symlink for lock ... Or rename it? ... Glen Barber ...
      (freebsd-questions)
    • Re: 6.1 and NFS
      ... This is becoming a show stopper for us moving forward with FreeBSD and may require us moving to a different OS (Linux or Solaris, ... Well, Solaris has the best NFS implementation out there and includes a number of subtle workarounds in their server code to reduce the number of and/or impact of problems seen doing heterogeneous networking against clients running other operating systems, but frankly, rpc.lockd isn't significantly more stable there on Solaris than on FreeBSD. ... In other words, if you plan to use NFS filesharing, you should make every effort to utilize software which functions with the classic ".lock"file mechanism rather than depending on lockf/flock/fcntl -based locking working. ... If a process wants the lock, ...
      (freebsd-questions)
    • Re: hard deadlock(?) on -current; some debugging info, need help
      ... > The thread in question is waiting on a nfs lock. ... > According to the vnode locks, there's one process waiting on the NFS ... > lock held by bash and 7 processes waiting on the ufs lock held by psi. ... I realize that the amd config file in which this ...
      (freebsd-current)