zsh-users
 help / color / mirror / code / Atom feed
* Weird error with clearcase
@ 2004-03-24 17:22 Seth Kurtzberg
  2004-03-25 17:17 ` Bart Schaefer
  0 siblings, 1 reply; 2+ messages in thread
From: Seth Kurtzberg @ 2004-03-24 17:22 UTC (permalink / raw)
  To: zsh-users

All,

This is clearly a clearcase problem and not a zsh problem, but I'm hoping
that the zsh gurus will be able to tell me why it might be happening.

When the default shell for a user is zsh, a the clearcase "setview"
command is invoked (clearcase version 6), zsh never starts.  Running
strace shows that an error is continuously occuring with the zsh history
file.  The error text says that an O/S call is being invoked to create a
cross device link.

In fact, no cross device link is being requested.  We moved the history
file around, our of home and onto /tmp and various other places, but the
behavior is unchanged.

Does this ring any bells for anyone?

Thanks in advance,
Seth Kurtzberg


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Weird error with clearcase
  2004-03-24 17:22 Weird error with clearcase Seth Kurtzberg
@ 2004-03-25 17:17 ` Bart Schaefer
  0 siblings, 0 replies; 2+ messages in thread
From: Bart Schaefer @ 2004-03-25 17:17 UTC (permalink / raw)
  To: zsh-users

On Mar 24, 10:22am, Seth Kurtzberg wrote:
}
} When the default shell for a user is zsh, a the clearcase "setview"
} command is invoked (clearcase version 6), zsh never starts.  Running
} strace shows that an error is continuously occuring with the zsh history
} file.  The error text says that an O/S call is being invoked to create a
} cross device link.

I suspect there's some subtlety here that strace output is not showing,
and that the history file itself is a red herring.

} Does this ring any bells for anyone?

I don't use clearcase, but I seem to recall from previous discussions here
that it presents the repository as a virtual filesystem.  My guess would
therefore be that the error really has to do with some access to that
filesystem.  Possibly the code that uses link() to create a lock file to
protect shared access to the history?

In which case it's not the location of the history file itself, but the
value of the $HISTFILE variable that would be at issue.  When you said ...

} We moved the history file around

... did you mean that you changed $HISFILE?


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-25 17:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-24 17:22 Weird error with clearcase Seth Kurtzberg
2004-03-25 17:17 ` Bart Schaefer

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).