Since he is an admin, he can easily do this by first setting up 
permissions and then enabling no_sharing.

Actually, I meant just allowing the admin to edit perms on his own 
shares....so he could create and make available "global" shares if 
desired...but yes, I agree, that is another issue.

Right, to disallow creating shares, locking the default_share pref (or 
default_tasklist, etc.) should do it.



Right now we have no way for an administrator to view all shares, so 
doing admin editing of permissions is way beyond the scope of this 
ticket...

The way I understood the no_share config setting, it is there to 
prevent user's from editing permissions on their shares, not for 
preventing them from being created.  IMO, it makes sense to continue 
to allow the creation of shares, even if the user is not allowed to 
edit the permissions.



...what I _do_ think we should do though, is allow an administrator 
the ability to edit permissions regardless of the no_share setting.

It turned out that the error message was coming from someone having 
edited the config file manually and not having set a source name for 
shares.

But we still have options to create new shares (not only in Turba).

I'm not seeing the error creating a share. Tried with both DT and SQL 
shares. Tries creating multiple new address books with no problem. 
Nuked my turba related database stuff and logged back in, default 
books were created fine....



The My AddressBook page _does_ still show, but I think that is as it 
should be.



Do you see exactly where it's failing?

If using the no_sharing option, Turba still show the "My Addres Books" 
page and tries to create new shares, but fails