*BSD News Article 84881


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.sprintlink.net!news-peer.sprintlink.net!news.charm.net!usenet
From: snowdog@charm.net (Sean Rolinson)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: Strange ksh shell problems with BSDI...
Date: Thu, 12 Dec 1996 20:31:23 GMT
Organization: Charm Net Inc.
Lines: 42
Message-ID: <58pq2s$bjd@news2.charm.net>
References: <4vagis$2vd@canton.charm.net>
Reply-To: snowdog@charm.net
NNTP-Posting-Host: stimpy.charm.net
X-Newsreader: Forte Free Agent 1.1/32.230
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:5439

Hello all,

We found the problem to be a permissions problem with the /usr
directory.

Sean Rolinson
snowdog@charm.net

snowdog@charm.net (Sean Rolinson) once said:


> Hello,

> We are converting from Unixware to BSDI on our telnet server.  I am in
> the process of converting all the users over.  I created a perl script
> that read a copy of /etc/passwd and shadow and created users from a
> list by reading those files.  It appeared to work well, and kept us
> from reiussing a ton of passwords.  My problem is that I am getting a
> weird shell error when logging in to the box.  When I log in, I get a
> message saying 'ksh: Cannot determine current working directory'.
> When I type pwd I get a message saying 'ksh: pwd: can't get current
> directory - Permission denied'.  When I type 'cd', the problem goes
> away and then everything seems fine.  I have also su'ed to root right
> after login and issued a 'pwd'.  It showed the /usr/home/snowdog
> directory from a pwd.  

> /usr/home, /usr/home2 and /usr/home3 are each 1 gig Partitions on
> several 2 gig Seagate drives.  Is it possible that these drives are
> the problem, or possible the way they are setup???  It is a strange
> problem.  I have tried chpass to change directory information, etc all
> to no avail.  Any help, suggestions would be greatly appreciated...

> Oh, this problem is only evident with ksh.  sh, tcsh, bash, etc all
> seem to work okay...

> Thanks...

> Sean
> snowdog@charm.net