Topic: Possible Bug? Owners/Groups

[Ian Lowe]

Using 5.6, fresh installation, I created a group "generic", then some ibays. The ibays have group r/w

Everything seems okay, *until* a user creates a file or folder within the ibay. At this point, rather than having owner root, group generic as expected, the newly created object has an owner and group of the user who created it.

Which means, of course, that no-one else can write to it, or edit it.

It seems that the "inherit permissions = yes" entry in smb.conf simply doesn't work

My work around was to edit the 90ibays template file, and add "force group = generic" and "force user = root". This is fine for my needs, but I figured it should be fixed...

I.

PS> incase anyone consider making this change themselves, bear in mind that "generic" is a specific group I have created. Ideally the template code should determine the group for each ibay, and "force group" that value instead.

[Guck]

I confirm. Additionally, when you manually change the ownership of files from user.user to user.group - and then you edit the files, the ownership is reset to user.user.

It makes web development particularly troublesome - you can't see what you've done until you change the ownership and mode of the files! Tedious.

Is there anyone out there (on 5.6) who *doesn't* suffer from this problem and would care to post the relevant sections from their smb.conf and the permission settings on their ibay folders?

G

[Guck]

Ian, I made the custom template you suggested out of 90ibays... and added, just below the line :

$result .= "inherit permissions = yes\n";

the lines :

my $group_bit = $properties{'Group'};
$result .= "force group = $group_bit\n";

and then expanded the template, restarted samba and things seem much improved...

Cheers,

G

[Ian Lowe]

Nice to know it's not just me... I tested your fix on my box Guck, and it works perfectly. the thing I don't understand is this:

If this issue affects everyone (and I don't see how it can't) Why isn't there an official bugfix for it?

Anyway, mutual support at it's best: thanks mate.

[Guck]

Ian Lowe wrote:
> If this issue affects everyone (and I don't see how it can't)
> Why isn't there an official bugfix for it?

Bloody good question... so how about it folks? Are Ian and I just special or is this something other people are experiencing too?

"No" is just as welcome as "Yes" here...

G

[Dan Brown]

Have you tried reporting this to bugs@e-smith.com?  The developers may or may not see this message, but they will see a bug report.

[Guck]

Well... I have great respect for the e-smith developers, and wanted to get some feedback about whether or not the community thought it was a bug before I added to their lists...

Isn't that the right way to go? What may be a bug to me, might be a feature to someone else...

Seriously though, I'd prefer someone get some confirmation about a bug before they submitted it to me.

G

PS. Hmm. I just realised the last (first) bug I submitted, I only sorta kinda got confirmation from the community about it... plus I had a pretty specific guess about what the problem / solution was...

[Charlie Brady]

Guck wrote:

> PS. Hmm. I just realised the last (first) bug I submitted, I
> only sorta kinda got confirmation from the community about
> it...

"the community" in this case was me, and I only commented because I happened to be looking here on my Sunday night "off".

Please  folks, report *all* suspected bugs to smebugs@mitel.com. We won't promise to fix them, but at least we can be sure to know about them, and can consider them in planning our Engineering work. There's no guarantee that anyone at Mitel will see what is posted on this board.

If you'd like confirmation, check your facts, and read the documentation before submitting your bug report. If you'd like to be extra helpful, use google to see what you can discover about the problem and include that in your report.

Regards

Charlie