[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

683.0. "Re: mskb failures on node ffox1" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Thu Apr 07 1994 18:32

Date Of Receipt: 	 7-APR-1994 17:14:27.42
From: 	FLUME::jmcg "Jim McGinness"
To: 	FLUME::darrell, decwet::connors, FLUME::jmf, FLUME::tea
CC: 	FLUME::odehelp
Subj: 	Re: mskb failures on node ffox1

This took too long to find....

Once we had another machine running 248.1 with access to the same
tools area and backing trees as ffox1, it became clearer and clearer
that the problem was local on ffox1.  I managed to confuse myself for
a while by typing in the wrong "mksb" command on gulch, but in the end
gulch worked fine and ffox1 was the only place where ODE failed.

In talking to Darrell, he mentioned that he had had a umask of 006
at one time and it caused him some pain.  He thought he had cleaned
everything up, but I used that information as a cue to look again for
unreadable directories.  This time, I found one in /share.

I was left with a bit of a mystery, though.  Why did the rebuilt
versions of bco not encounter the error?

They got rebuilt shared,
...so they ended up using the new getwd algorithm,
.....which short circuits part of the ../../.. search
........by locating the mount point of the current file system
...........with the statfs() call.
They never tried to open /share.

The failing versions were built static and so had the old version of
getwd(), which always backtracks all the way down to /.

Case closed.

T.RTitleUserPersonal
Name
DateLines
683.1Re: mskb failures on node ffox1SMURF::FILTERAutomatic Posting Software - mail to flume::puckThu Apr 07 1994 18:329
Date Of Receipt: 	 7-APR-1994 17:17:15.59
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE"
To: 	connors%[email protected], [email protected],
	[email protected], [email protected], [email protected]
CC: 	[email protected]
Subj: 	Re: mskb failures on node ffox1

Jim, good detective work!	-josh

683.2Re: mskb failures on node ffox1SMURF::FILTERAutomatic Posting Software - mail to flume::puckThu Apr 07 1994 19:3714
Date Of Receipt: 	 7-APR-1994 17:37:07.10
From: 	WASTED::"[email protected]" "Darrell A. Dunnuck  07-Apr-1994 1737"
To: 	[email protected] (Jim McGinness)
CC: 	[email protected], connors%[email protected],
	[email protected], [email protected], [email protected],
	[email protected]
Subj: 	Re: mskb failures on node ffox1

Great job tracking this down Jim.

Sheepishly,

Darrell

683.3Re: mskb failures on node ffox1SMURF::FILTERAutomatic Posting Software - mail to flume::puckFri Apr 08 1994 00:4613
Date Of Receipt: 	 7-APR-1994 23:20:22.45
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected] (Jim McGinness)
CC: 	[email protected], decwet::connors, [email protected], [email protected],
	[email protected]
Subj: 	Re: mskb failures on node ffox1

Wow! I'm impressed. Nice work.
-- 
 Grant Van Dyck 		enet:    [email protected]	
 Release Engineering