G.Eustace@massey.ac.nz (Glen Eustace) (11/14/90)
Prior to the installation of OSx5.0 we used to get a situation occuring which I had hoped was a thing of the past, no such luck as it has just happened again. Generally speaking it is 'find' that finds this problem but other utilities don't like it either. The problem is an entry in a directory with no name, yes that is a name field of zero length where the remainder of the entry corresponds exactly to the info in '.' 'find' gets all upset and complains lots of times about not being able to stat the an entry or getting a bad status for an entry. The entry it complains about is usually one of the other files in the same directory. As the entry for '.' changes i.e. size etc, so does the entry for our mysterious imposter ! In order to get rid of this situation we; 1. mv the directory to lost+found 2. create a new directory in the correct place 3. mv all the good files into the new directory 4. unlink the rogue directory 5. wait for the next 'fsck' to complain about it 6. allow 'fsck' to tidy up. Can anyone shed any light on what may be causing these entries and whether our approach to cleaning them up can be improved. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Glen Eustace, Software Manager, Computer Centre, Massey University, Palmerston North, New Zealand. EMail: G.Eustace@massey.ac.nz Phone: +64 63 69099 x7440, Fax: +64 63 505 607, Timezone: GMT-12