Re: Directory???

G'day All,


Thanks for the suggestions.


I doubt the 'find' suggestion as I don't recall doing anthing such
as that.

cxoffice is gone so if that caused the problem that's another good
reason to be rid of it. It didn't work for me at all.




On Thu, 21 Jul 2005 22:33:12 +1000  Ben Stringer <[email protected]>
wrote:

> On Thu, 2005-07-21 at 20:41 +1000, Keith Bainbridge wrote:
> > G'day folks,
> > 
> > What do youthink I have done to get this:
> > 
> > /disks/net/b120/hda4/home/keith/.cxoffice/dotwine/dosdevices/ZS
> > XKM0
> > ~L/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/1
> > 4543
> > /task/14543/root/proc/14543/task/14543/root/proc/14543/task/145
> > 43/r
> > oot/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/
> > 1454
> > 3/task/14543/root/proc/14543/task/14543/root/proc/14543/task/14
> > 543/
> > root/proc/14543/task/14543/root/proc/14543/task/14543/root/proc
> > /145
> > 43/task/14543/root/proc/14543/task/14543/root/proc/14543/task/1
> > 4543
> > /root/proc/14543/task/14543/root/proc/14543/task/14543/root/pro
> > c/14
> > 543/task/14543/root/proc/14543/task/14543/root/proc/14543/task/
> > 1454
> > 3/root/proc/14543/task/14543/root/home/keith/keithdata/steph/et
> > ax20 03/LUKE.TAX
> > 
> 
> Ran "find" over the /proc directory and passed the result to
> something else that creates files?
> 
> /proc/<PID>/task/<PID>/root is (usually) a symlink to "/", so that
> kind of makes all the middle part of that path make sense. Why
> this path got constructed out of parts of your personal files and
> a recursion over /proc will be interesting to hear :)
> 
> Perhaps CrossOver Office is looking in /proc and treating it like
> a normal filesystem?
> 
> Or maybe the shell got passed some odd combination of characters
> that "resolved" to the PID entry in /proc ?
> 
> Cheers, Ben
> 
> 


-- 
Keith Bainbridge
PO Box 324
BELMONT   Vic   3216  OZ
+61(0)3-5241-1881
[email protected]
[email protected]