← Back to team overview

touch-packages team mailing list archive

[Bug 132459] Re: Store intensively accessed cache files in /tmp instead of in nfs-mounted /home

 

Could you propose this as a guideline or possible risk that all
packagers should look at when packaging?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/132459

Title:
  Store intensively accessed cache files in /tmp instead of in nfs-
  mounted /home

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Some applications like Google Earth, Povray and many many more store
  volatile but intensively accessed cache files in /home. When /home is
  NFS-mounted this causes for unnecessary network load and processing
  power which slows down the local network and the application.

  When these applications are aware that their cache directory is in an
  NFS-mounted location, the could (or perhaps should) store their
  volatile but intensively accessed cache files in /tmp. (Of course with
  the proper accessing rights.)

  This features should be implemented in the applications themselves.
  These will have to be identified first. Perhaps also the system has to
  have to information that it is desirable that in case /home is NSF-
  mounted, that these applications store their volatile but intensively
  accessed cache files in /tmp. Or the system can confirm that all
  should be in /home no matter if it is NFS-mounted of not.

  Implementing this feature will allow for less network traffic, less
  processing power begin consumed which will result in higher user
  satisfaction and less wasting of energy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/132459/+subscriptions