| Date Of Receipt: 18-MAR-1994 14:19:54.53
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE"
To: [email protected], [email protected]
CC: [email protected], [email protected]
Subj: Re: ODE Complaint/suggestion
Pete, was the problem here with ownership of kxct.conf files - as I said in
previous mail - you had to replace links to devbld-owned file with real files
owned by the sharedsb owner?
If so - I'm PTTing (like QARing) this problem... Thanks... -josh
(command = gen-ptt)
-------
From [email protected] Wed Mar 16 16:53:10 1994
Delivery-Date: Wed, 16 Mar 94 16:53:14 -0500
Return-Path: [email protected]
Received: from abyss.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/04Mar94-1219PM)
id AA29261; Wed, 16 Mar 1994 16:53:10 -0500
Received: by abyss.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
id AA07954; Wed, 16 Mar 1994 16:52:32 -0500
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: ODE Complaint/suggestion
Date: Wed, 16 Mar 94 16:52:32 EST
From: Peter "If the software don't work, rewire the hardware" Schulter <[email protected]>
Status: RO
I just spent all afternoon tracking down a problem with my shared sandbox
that I probably would have found much faster if ode had given me a more
meaningful error message. The problem was that kxctd (running as root)
did not have access to a directory in the shared sandbox. However, ode (bsubmit)
did not give me an EACCESS or EPERM (or a message like "can't access ..."),
but the message:
kxct: Invalid kxct config:
/usr/projects/netode2/atm/sandbox/atm/logs/kxct.conf
read failed: Error 0
This lead me to believe that something was wrong with the file contents since ode
seemed to be telling me that it was reading the file (read failed with an error 0
which implies the read succeeded) and just didn't like the contents of the file.
If it had said somethile like "can't access file" permissions on directories
would have been the first thing I would have looked at. I spent hours editing
the file trying to find the offending entry.
Someone should put this on their list of things to fix/improve in ode.
Thanks,
--- pete
w
|
| Date Of Receipt: 18-MAR-1994 14:47:03.67
From: ABYSS::schulter "Peter Schulter USEG"
To: abyss::jmf
CC: [email protected], [email protected], [email protected]
Subj: Re: ODE Complaint/suggestion
> Pete, was the problem here with ownership of kxct.conf files - as I said in
> previous mail - you had to replace links to devbld-owned file with real files
> owned by the sharedsb owner?
No, the problem was with the permissions of one of the directories in the
shared sandbox. Replacing the devbld-owned link wasn't the fix, the fix
was making the directory modes 755 so that the kxctd could open a file in it.
My complaint is that the message I got from ODE gave no indication that
it could not open a file because of permissions problems. It lead me
to believe it could access the file, but that the file contents were
bogus.
> If so - I'm PTTing (like QARing) this problem... Thanks... -josh
> (command = gen-ptt)
Thanks,
--- pete
|