Hello All!!
I wonder if anyone can comment on the following .....
Using SME 6.0, create two ibays.
ibay 1 .....
Name: t1
Desc: t1
Group: Admin
User Access: Write = Admin, Read = Group
Public Access: No access
Exec of dyn content: Disabled
ibay 2 .....
Name: t2
Desc: t2
Group: Everyone
User Access: Write = Group, Read = Everyone
Public Access: FULL access
Exec of dyn content: Enabled
Now look at the ibays using the File Explorer on a Windows 98 box.
t1 cannot be seen - that's OK because of the ownership
t2 can be seen
Now modify t1 so that
Owner Group = Everyone
User Access: Write = Group, Read = Group.
Using the Windows explorer again ...
t1 can be seen, is empty, and can have things created in it (say fred.txt)
Looking now at t2
t2 can be seen, contains directories .AppleDesktop, files, html, and cgi-bin. Cannot create anything in here (no error messages given by Windows)
Go to \files and everything works OK - a file can be created (say jim.txt)
Now, to me, this seems to be inconsistant behaviour. In the first instance the Linux directory /home/e-smith/.../ibays/t1/files is presented to the Windows explorer as //Server/t1. In the second instance the directory /home/e-smith/.../ibays/t2 is presented as //Server/t2 and the /home/e-smith/.../ibays/t2/files directory is seen as //Server/t2/files. I would have expected the ibays to appear the same to Windows.
The difference seems to be that in the t1 case the directories (in the Linux world) end up as admin:shared whereas the t2 files end up as root:shared.
Now, as I was using the SME6 administration 'web site' to do all this, I must come to the conclusion that what I see is an undocumented feature (!) and so I just thought I would document it and see if anyone can tell me why this happens.
Regards,
Dave