Forum Replies Created
-
Posts
-
.. Ok, I removed /Library/Perl entirely and also the “PerlBackup” which the installer created, then I reinstalled from the Pkg. Still the same error though..
Even tried to reboot, as if it would help 😥
//Didde.
I meant “dc=” may not work with the local netinfo db. also, there has to be a mail= entry under the username in the netinfo db, which didn’t come out as clearly as I thought when I typed the other post, sorry, Dan
Hi,
I actually got this to work last night after some tinkering. I had to leave out the ‘dc=’ bits from the Address Book setup. Just ‘cn=users’ made it work, as long as there was a ‘mail=’ entry in the netinfo db. I made a /contacts folder in the netinfo db with a folder in there with a ‘mail=’ and ‘telephonenumber=’ entry and it also worked as long as I left out the ‘cn=’ entries in address book LDAP config.
cn= mabye doesn’t work with local netinfo dbs? That’s all I could think of.
hope that helps,
DanI’m trying this on 10.2.4 Client, without success.
I could browse the local Netinfo database using the 3rd-party LDAP app “LDapper”, but the local Addressbook application didn’t work. (I tried both adding properties in the /users CN, and making a separate /addressbook).
From another computer on the subnet, neither the LDapper nor the Addressbook worked, though the debug showed an attempted connection.
Has anyone worked this out? Is there any reason to think I can get it going on Client without too much difficulty?
I do not agree…. first of all, in my opinion, world writeable means something like drwxrwxrwx (with the W in the third position). Second, try to log in with your settng! Yes, I can login but when you try to upload something, you can’t!
At the beginning I used your same setting, thinking to have solved the problem because of the fact I could login… but once logged in I couldn’t upload nothing.Try and let me know your results. Consider I am on 10.2.3 CLIENT, not server. Probably some settings work different… (I am not so expert)
Lukas
If I’m not mistaken, /NetInfo/root is the network domain. It automatically receives the “network” tag in NetInfo.
When you configure a share to automount in Workgroup Manager, choose “/NetInfo/root” for the “Mount volume for all users in…” option
Brandon Houston
I’ve got the same problem. I’ve tried changing permissions and recreating the log files but exim still gets a permission denied when trying to access the log files. Then, the exim process stops.
Any help is appreciated.
ok i feel a ittle better now ( knowing that i couldn’t find it ).
Anyhoo. i did install the DB in a local directory and things seem to be okay. Thanks for the heads up on the weirdness i may encounter.
–jeff
try to use the ‘pico’ text editor from the command line to edit those files. Just issue the command pico /etc/racoon/racoon.conf and it will open that file up inside the shell. Use your arrow keys to move around, delete to .. delete .. etc …
Also, try out http://www.accesswave.ca/alrankin/ and see if any of the info I posted can help you out.
there is no ‘default’ root password.
The ‘default’ setup uses sudo to pass the administrator credentials to the OS. If necessary, you will have to enable the root account through the NetInfo manager.
I have been fighting with the same problem, and what I finally figured out is that proftpd is extremely picky about what it will accept re:mysql.
I have found that it will reject a login with correct username and password if the “homedir” provided in mysql is not accessible. I can only assume that it will not allow connection until it perfoms the chroot, and so if the path doesnt exist, or your ftpuser on the system does not have priveledges on that folder, then it refuses to authenticate.
So far I have found no way to make mysql auth work without the userdirectory being world writable, either. Not terribly dangerous after the chroot, and you block execute, but still not my favorite attribute. Anyone else have better luck?
When setting up your users and groups in the Workgroup Manager, which NetInfo Domain do you use when creating your new groups? If you create a new group in the “NetInfo/root” you may have problems.
I did not pay attention to which Domain was active when creating my groups and they were all in the “NetInfo/root”. They should be in the NetInfo Domain “NetInfo/DefaultLocalNode”. After making the switch most but not all of my permissions problems went away.
