[Date Prev][Date Next]
Permissions, users, startup when install from source
- To: firstname.lastname@example.org
- Subject: Permissions, users, startup when install from source
- From: Ori Bani <email@example.com>
- Date: Tue, 15 Jan 2013 13:32:52 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BCyS0a3EqV4Qa8UHHtw3lRQ6r+CxSBFQEWPs8Yu9QdY=; b=R7hb0Rr7JiRDml9WyXvQ8iGjs+UW81HiW7Rrgg4bDNk5sl2daBggme/VhI97ItMkHB t6IQ1jrbg9mPlYyFBZHYyS2re+MjmOC3f1ZRB3wjLMRc/Hhqa1+vYuIEEvB7dgnsd+N+ bv+1yEOlgq1YefCgYTOXw8XBVyMRlbrshNNZRRurOA7gTccyu131cOqvx0TbnbaNAFUx spGvqMgOWynh3CSltRBZwwRpurbwoC4bsrwKFjRpmk6m3xFnajgO3lMLDyQboMnl0hBd /fsp998XuoPR5+NxzoQvwSddTQRKRkFQRWYZAm9pL8wEjooCteV//ykUA8zcZtsht2EG 5P4A==
If compiling and installing from source, I don't see any information
in the manual about how to auto-start the software and about
process/file/directory permissions and ownership. I'm still searching
the Faq-O-Matic (which is a little frustrating).
Taking a step back, I'd love to install from yum on RHEL/CentOS and
let it be taken care of in a trusted manner. But we require better
password hashing than SHA1, so we are required to compile by hand
using the passwd/sha2 contributed module (little surprised this isn't
accepted into the core project, but I'm sure there are reasons).
Maybe I can find this in a third-party repo somewhere?
After installation, what is commonly done in this regard? Create
user/group "ldap" with no login shell and chown ldap:ldap on
/usr/local/var/openldap-data? Is that all?
Then what do people use for auto-starting the software (presumably
with -u ldap -g ldap) in a RedHat environment?
Thanks for the work that you do, thanks for the great software.