[jira] [Commented] (JENA-1101) Fuseki filesystem layout and Linux FHS

["Joachim Neubert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061650#comment-15061650 ] 

Joachim Neubert commented on JENA-1101:
---------------------------------------

{noformat}

# rpm -ql tomcat
/etc/logrotate.d/tomcat
/etc/sysconfig/tomcat
/etc/tomcat
/etc/tomcat/Catalina
/etc/tomcat/Catalina/localhost
/etc/tomcat/catalina.policy
/etc/tomcat/catalina.properties
/etc/tomcat/context.xml
/etc/tomcat/log4j.properties
/etc/tomcat/logging.properties
/etc/tomcat/server.xml
/etc/tomcat/tomcat-users.xml
/etc/tomcat/tomcat.conf
/etc/tomcat/web.xml
/usr/bin/tomcat-digest
/usr/bin/tomcat-tool-wrapper
/usr/lib/systemd/system/tomcat.service
/usr/lib/systemd/system/tomcat@.service
/usr/lib/tmpfiles.d/tomcat.conf
/usr/libexec/tomcat
/usr/libexec/tomcat/functions
/usr/libexec/tomcat/preamble
/usr/libexec/tomcat/server
/usr/sbin/tomcat
/usr/share/doc/tomcat-7.0.54
/usr/share/doc/tomcat-7.0.54/LICENSE
/usr/share/doc/tomcat-7.0.54/NOTICE
/usr/share/doc/tomcat-7.0.54/RELEASE-NOTES
/usr/share/tomcat
/usr/share/tomcat/bin/bootstrap.jar
/usr/share/tomcat/bin/catalina-tasks.xml
/usr/share/tomcat/conf
/usr/share/tomcat/lib
/usr/share/tomcat/logs
/usr/share/tomcat/temp
/usr/share/tomcat/webapps
/usr/share/tomcat/work
/var/cache/tomcat
/var/cache/tomcat/temp
/var/cache/tomcat/work
/var/lib/tomcat
/var/lib/tomcat/webapps
/var/lib/tomcats
/var/log/tomcat
/var/log/tomcat/catalina.out
/var/run/tomcat.pid
{noformat}

> Fuseki filesystem layout and Linux FHS
> --------------------------------------
>
>                 Key: JENA-1101
>                 URL: https://issues.apache.org/jira/browse/JENA-1101
>             Project: Apache Jena
>          Issue Type: Improvement
>    Affects Versions: Fuseki 2.3.1
>            Reporter: Joachim Neubert
>
> When it comes to filesystem layout, the Java/Tomcat/Webapps world differs quite fundamentally from the Linux world: Whereas for Tomcat or Fuseki it is quite normal to have all files under a common root directory, the [Linux Filesystem Hierarchy Standard|https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard] (which is followed by most distributions) provides multiple roots for application files:
> Configuration goes to /etc, read-only files to /usr, variable files to /var (./log, ./cache etc.). To give you a better idea what this means in practice, I add the layout of the tomcat installation by Centos 7 RPM as an example.
> From a linux sysadmins point of view, this makes it easy to know where to find stuff without any special knowledge of the application, and to generalize tasks like backup (e.g. exclude all application cache files on the system).
> On the other hand, this means considerable more work, if you have to cover systems outside the Linux world too. Things may get even more complicated by remaining differeces between distributions and SElinux policies.
> So I don't suppose FHS compatibility is an realistic option for Fuseki.
> Yet, the current handling of mapping $FUSEKI_HOME/run to /etc/fuseki, with the whole bunch of assorted runtime files, feels profundly wrong. According to FHS, I would expect something like
> {noformat}
> etc/
>   fuseki/
>     config.ttl
>     shiro.ttl
>     conf.d/
>       service1.ttl
>       ...
> {noformat}
> and all the other stuff elsewhere.
> So I wonder if it would be possible to put the config hierarchy above under a, say, $FUSEKI_CONF root, which defaults to /etc/fuseki in the .war installation, and to $FUSEKI/conf otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)