Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ncrlnk!ncrwic!srwic!srwic.uucp!sralston From: sralston@srwic.uucp (Steve Ralston) Newsgroups: comp.unix.sysv386 Subject: Problems with getwd() on V.4.2 with UFS file system? Keywords: getwd, Release 4, UFS, S51K, s5, file system Message-ID: <198@srwic.UUCP> Date: 29 Nov 90 06:58:40 GMT Sender: sralston@srwic.UUCP Organization: Steve Ralston Wichita, KS Lines: 28 I seem to have stumbled across a problem while running some RCS programs (Revision Control System) on a system running UNIX V.4.2 OS. The system is a NCR PC486/Microchannel 33 MHz running a BETA version of NCR UNIX System V, Release 4 Version 2, if that info is applicable. These are RCS binaries compiled on a SCO ODT system, which would have been my first guess as root cause of the problem. The strange thing is that all worked fine UNTIL I reinstalled the OS using a (faster?) UFS root file system, instead of the s5 (S51K) root file system which I had been using. The error returned by the RCS `ci` (check-in) program looks something like: ci error: can't build current directory path ci aborted ci error: can't find semaphore file RCS/,, Looking thru the RCS source code, the fatality appears to hinge on the following snippet of C code in ci.c: if (getwd(pathbuf)==NULL) faterror("Can't build current directory path"); So it appears that the call to getwd() works for a S51K file system, but does NOT work (returns NULL) for a UFS file system. Ideas, anyone? -- Steve Ralston sralston@srwic.UUCP 235 N Zelta voice: 316-686-2019 Wichita, KS 67206 ..!uunet!ncrlnk!ncrwic!srwic!sralston