It would be nice in our environment if those installation tasks which
require root were separated from those that don't. I would prefer to
compile software as, say, user 'arvin' and then execute only those tasks
which absolutely need to run as root as root -- creating system directories,
new users and groups, and setting file and directory modes. I'd like to
separate the configure and compilation processes from the installation process.
In our environment, our source directory is automounted from a separate machine
than where I want to install the software. Root on the installation machine
doesn't have authority to overwrite the source files owned by 'arvin' on the
source machine, so unless I make the source files world-writable I can't
compile ossec as root. But I can't create users or set directory permissions as
'arvin'. So I will have to hack the install scripts for each release unless
this
is changed. (Nevertheless, I'm very pleased to see indications that the source
is
updated frequently!)
It would also be nice if the install script would only try to create the users
and group if they do not already exist.
My department is very pleased with ossec's capabilities. We were looking for
a cross-platform HIDS product and were excited to find this. It works very well
out of the box and seems very extensible. Wish me luck when I try to compile it
for HP-UX.
-- Leslie Arvin
[EMAIL PROTECTED], Office: FREH G409, Phone: 765-496-3971
Network Systems Administrator, ITI-Unix Platforms
Purdue University, Information Technology at Purdue
--~--~---------~--~----~------------~-------~--~----~
-~----------~----~----~----~------~----~------~--~---
