I have installed orion in my gentoo linux box and I have been doing some minor changes in the ebuild to set more restrictive perms over the orion files without affect it's functionality. Here I attach the new ebuild that have the new perms: --- /usr/portage/www-servers/orion/orion-2.0.5.ebuild 2005-01-08 03:38:09.000000000 +0100 +++ orion-2.0.5.ebuild 2005-03-13 04:03:49.000000000 +0100 @@ -31,7 +31,7 @@ src_install() { # CREATE DIRECTORIES - diropts -m0775 + diropts -m0755 dodir /opt/${PN} dodir /opt/${PN}/config dodir /opt/${PN}/sbin @@ -52,7 +52,7 @@ cp -a ${FILESDIR}/${PV}/orion.conf ${S}/orion insinto /etc/conf.d - insopts -m0750 + insopts -m0644 doins ${S}/orion # CREATE DUMMY LOG & PERSISTENCE DIR @@ -92,7 +92,7 @@ chown -R orion:orion /opt/${PN} || die "Failed to chown in /opt" chown -R orion:orion /var/log/${PN} || die "Failed to chown in /var/log" - chown orion:orion /etc/conf.d/orion + chown root:root /etc/conf.d/orion || die "Failed to chown in /etc/conf.d" einfo " " einfo " NOTICE!" Also I have changed the restart function on the /etc/init.d/orion startup script to be more standard: restart() { svc_stop; svc_start } Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: The orion files have more restrictive perms, but it doesn't affect. The restart function on startup script is more standard.
*** Bug 85033 has been marked as a duplicate of this bug. ***
patch partially applied, thanks
