Weird. I was pretty sure that we always installed to
/opt and not /usr/local. At least that’'s what it says
in the installer tool. Are you seeing the RPM install
to /usr/local on your box?
My apologies. I had /usr/local/bin/messenger because someone else had created it on my machine.
Do you think it’'s a “best practice” for an RPM to do
the init.d changes? I’'ve been told by others that
most admins would rather create the init.d setup
themselves, but I’'m open to all opinions.
Well, as a former RPM maintainer, that’'s what I did. And this is what it seems everyone is still doing.
FreshRPMs does it (http://freshrpms.net/). Example: http://stentz.freshrpms.net/rpm.html?id=299
Packman does it (http://packman.links2linux.org). Example: http://packman.links2linux.org/?action=615
And this is also what RPMs from the distribution maintainers do.
I’'m not aware of any lock files. Do we have some
Correct me if I’‘m wrong, but isn’'t embedded-db/messenger.lck a lock file?
- put all log files in /var/log/…
I’'d like to avoid that. By having the logs always in
a consistent place, that lets us do the log viewer in
the admin console and document exactly where people
look for logs in a cross-platform manner.
Yes, that’‘s the advantage, and I figured this is why you guys were putting everything under the Jive installation directory. It’‘s a choice between convenience and consistence, and standards-compliance and a shred of extra security, IMHO. Your choice allows Windows server admins to know exactly where the log file would be on a Linux installations of Jive, although a seasoned Linux sysadmin with no prior knowledge of Jive would wonder why he/she can’'t make /opt read-only, and gripe about its non-compliance to the FHS.
Thanks for the response, Matt, and keep up the great work!