From: Daniel H. <da...@hi...> - 2003-03-21 04:10:41
|
Here is some more specific information. The file server, Nori, has two generally used shares. One called "Public" and the other "Service Media". In Service Media the __db* files are created thus: -rw-rw-rw- 1 daniel daniel 8192 Feb 24 11:25 __db.001 -rw-rw-rw- 1 daniel daniel 270336 Feb 24 11:25 __db.002 -rw-rw-rw- 1 daniel daniel 344064 Feb 24 11:25 __db.003 Notice the permissions are correct to permit others to write to the files. On the Public volume, the __db* files are creataed thus: -rw-r--r-- 1 nobody nobody 8192 Mar 20 15:49 __db.001 -rw-r--r-- 1 nobody nobody 270336 Mar 20 15:49 __db.002 -rw-r--r-- 1 nobody nobody 344064 Mar 20 15:49 __db.003 This causes a problem. If I am the first to log in then only I can access the files. If another user logs in as guest first then I cannot access the files. My afpd is as follows: /data/atalk/servicemedia "Service Media on Nori" allow:daniel,greg,jake,joel,nobody,tony,wendy rolist:nobody /data/atalk/public "Public on Nori" (The first item is all on one line) Any ideas why this is happening? Daniel On 3/20/03 11:15 AM, "Daniel Hazelbaker" <da...@hi...> wrote: > I have also had this happen when the _db* temporary files are not rw to the > user they also get an empty volume list. And for some reason I keep getting > those as owned by me on my secondary server. Here is the scenario: > > Everybody accesses Public volume as guest with read only access. > I access it as me with read write access. > Every once in a while they call me and say they can not see any files. > I go and look at the server and the _db* files are owned by me and are > u=rw,g=r,o=r, so they can not be touched by them and thus they can not see > any files. > > This is a recent development, and it seems to be random? > > Daniel |