I’ve got 3 questions about bc_desktop which got me confused.
the files under
/var/www/ood/apps/sys/bc_desktopare shipped with the ondemand rpm. However, the form does not specify a cluster, so it is invalid and not shown by default on the portal. If my understanding is correct, this directory gets parsed every time someone logs in and will fail by default. This seems wrong to me as it slows down the portal. Am I missing something? It seems to me this directory should not be included in the rpm.
At our site we use xfce. Previously we already installed the bc_paraview app. Now when I look at how bc_paraview starts xfce and how bc_desktop starts xfce, these are completely different. For instance:
- bc_desktop works in the user home dir, while bc_paraview works in the job directory.
- bc_desktop starts xfce-session, bc_paraview xfwm directly without session management.
- bc_desktop does not configure dconf, bc_paraview does configure it
I’m wondering why the difference? Are there good reasons or is this just maintained by different people?
in addition to previous question, is there a way to share the startup method of xfce between several apps? Most of our predefined apps will/should use the same way. I feels prone to error to copy the same files everywhere. Is there a way to source scripts/erb files/… from a common place?