search for: parent_dir

I recently upgraded to Samba 3.0.37 (not the most current but when running 2.0.x it was a big step.) However I now have an issue I just can't seem to fix, being entirely possible I stared at it for a week without seeing it. The old version used to inherent the GID from the parent directory. I can honestly say I have no idea how I configured that to work but it was seven years ago and

I was flipping through the code recently and noticed that we still have the double whammy of allocating dir entry positions with parent_dir->counter++ and that weird setting of f_pos to 2^31-1. So after enough creates (and deletes :)) in a directory we end up with an entry item whose key is past that value. f_pos gets rewound instead of being set to that magical EOF. readdir() gets stuck returning the entries after INT_MAX over a...

...return status; > } > @@ -1319,9 +1312,8 @@ static int acl_common_remove_object(vfs_handle_struct *handle, > goto out; > } > > - DEBUG(10,("acl_common_remove_object: removing %s %s/%s\n", > - is_directory ? "directory" : "file", > - parent_dir, final_component )); > + DBG_DEBUG("removing %s %s/%s\n", is_directory ? "directory" : "file", > + parent_dir, final_component); > > /* cd into the parent dir to pin it. */ > ret = vfs_ChDir(conn, parent_dir); > @@ -1354,10 +1346,9 @@ static...

On Fri, Aug 26, 2016 at 04:03:49PM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 02:46:19PM -0700, Jeremy Allison via samba wrote: > > On Fri, Aug 26, 2016 at 06:44:05PM +0200, Ralph Böhme wrote: > > > > > > Cheerio! > > > -slow > > > > Still reviewing this - but a few things that will need changing: > > > > When adding the