The ebuilds create the resin user/group but do not chown the appropriate files resulting in installations that will not start. I tested both the resin 3.0.8 and 2.1.14 ebuilds on two up to date gentoo boxes and experienced similiar results. At the very least, the ebuilds need to: chown -R resin:resin /opt/resin chown -R resin:resin /var/log/resin chown -R resin:resin /etc/resin chown -R resin:resin /usr/share/resin Furthermore, the ebuilds create a configuration file /etc/conf.d/resin, but I am unable to find anywhere the contents are actually read and processed during resin startup. There does not appear to be a "source /etc/conf.d/resin" in either /etc/init.d/resin, /opt/resin/bin/httpd.sh, or /opt/resin/bin/wrapper.pl. Any significant resin site will need to set appropriate java options...and it is highly misleading and potientially dangerous for the configuration file to appear to accept them but not process. Finally, some symbolic links just weren't setup... /etc/resin/conf -> /opt/resin/conf /var/log/resin -> /opt/resin/log I believe these ebuilds need significant review.. Reproducible: Always Steps to Reproduce: 1.install resin 2.try to use it 3. Actual Results: many many failures Expected Results: run
I fixed the symlink and the conf chown in 3.0.8 also added a check if /opt/resin/conf is a dir (from 2.* ebuilds), and if it is, i move the files too (/etc/resin/conf.old). So that portage can created the symlink. Why does resin need to own /usr/share/resin(/lib) ? It should only be able to read from those, and it can... /etc/conf.d/resin is sourced automaticly in /etc/init.d/resin by runscript I don't use resin myself, only test i (can) run are the examples If you have any other comments please let me know.
