[Touch-packages] [Bug 1415974] Re: Cleaning a directory in /tmp during boot updates the directory's modification time

2015-04-14 Thread Ken Sharp
Indeed the script shows that the directory's mtime is checked after the
files have been removed:

DEXPR="-mtime +${TMPTIME} -ctime +${TMPTIME}"

find . -depth -xdev $DEXPR $EXCEPT -type d -empty -delete

** Package changed: sysvinit (Ubuntu) => mountall (Ubuntu)

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

Title:
  Cleaning a directory in /tmp during boot updates the directory's
  modification time

Status in mountall package in Ubuntu:
  New

Bug description:
  When TMPTIME is set to anything other than 0 (clean all of /tmp) in
  /etc/default/rcS, /tmp is cleaned of "old" files, but in doing so it
  updates the modification times of all the directories, so that they
  remain until they themselves become "old".

  I hope this makes sense, an example:

  During boot files in /tmp older than three days will be cleaned.
  Files in /tmp/olddir will be cleaned.
  /tmp/olddir will have its modification time updated, it is no longer an old 
directory.
  /tmp/olddir is left behind because it is not recognised as an old directory.

  It's minor and may be impossible to fix, but is there any magic that
  can be done to remove the old directories at boot rather than waiting
  for the directory to "expire" again? Is it possible to avoid the
  modification time being updated?

  Simply removing the whole directory based on its creation or
  modification times, without first checking its contents for newer
  files, would probably not be preferable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Thu Jan 29 15:13:27 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1415974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1415974] Re: Cleaning a directory in /tmp during boot updates the directory's modification time

2015-04-14 Thread Ken Sharp
** Description changed:

- When set to anything other than 0 (clean all of /tmp), /tmp is cleaned
- of "old" files, but in doing so it updates the modification times of all
- the directories, so that they remain until they themselves become "old".
+ When TMPTIME is set to anything other than 0 (clean all of /tmp) in
+ /etc/default/rcS, /tmp is cleaned of "old" files, but in doing so it
+ updates the modification times of all the directories, so that they
+ remain until they themselves become "old".
  
  I hope this makes sense, an example:
  
  During boot files in /tmp older than three days will be cleaned.
  Files in /tmp/olddir will be cleaned.
  /tmp/olddir will have its modification time updated, it is no longer an old 
directory.
  /tmp/olddir is left behind because it is not recognised as an old directory.
  
  It's minor and may be impossible to fix, but is there any magic that can
  be done to remove the old directories at boot rather than waiting for
  the directory to "expire" again? Is it possible to avoid the
  modification time being updated?
  
  Simply removing the whole directory based on its creation or
  modification times, without first checking its contents for newer files,
  would probably not be preferable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Thu Jan 29 15:13:27 2015
  MarkForUpload: True
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)

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

Title:
  Cleaning a directory in /tmp during boot updates the directory's
  modification time

Status in sysvinit package in Ubuntu:
  New

Bug description:
  When TMPTIME is set to anything other than 0 (clean all of /tmp) in
  /etc/default/rcS, /tmp is cleaned of "old" files, but in doing so it
  updates the modification times of all the directories, so that they
  remain until they themselves become "old".

  I hope this makes sense, an example:

  During boot files in /tmp older than three days will be cleaned.
  Files in /tmp/olddir will be cleaned.
  /tmp/olddir will have its modification time updated, it is no longer an old 
directory.
  /tmp/olddir is left behind because it is not recognised as an old directory.

  It's minor and may be impossible to fix, but is there any magic that
  can be done to remove the old directories at boot rather than waiting
  for the directory to "expire" again? Is it possible to avoid the
  modification time being updated?

  Simply removing the whole directory based on its creation or
  modification times, without first checking its contents for newer
  files, would probably not be preferable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Thu Jan 29 15:13:27 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1415974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1415974] Re: Cleaning a directory in /tmp during boot updates the directory's modification time

2015-02-12 Thread Ken Sharp
If a directory in /tmp has multiple subdirectories it means that the
director[y|ies] can hang around for months, or even permanently. This
shouldn't use a lot of disk space but will leave /tmp a bit of a mess.

** Tags added: amd64 trusty

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

Title:
  Cleaning a directory in /tmp during boot updates the directory's
  modification time

Status in sysvinit package in Ubuntu:
  New

Bug description:
  When set to anything other than 0 (clean all of /tmp), /tmp is cleaned
  of "old" files, but in doing so it updates the modification times of
  all the directories, so that they remain until they themselves become
  "old".

  I hope this makes sense, an example:

  During boot files in /tmp older than three days will be cleaned.
  Files in /tmp/olddir will be cleaned.
  /tmp/olddir will have its modification time updated, it is no longer an old 
directory.
  /tmp/olddir is left behind because it is not recognised as an old directory.

  It's minor and may be impossible to fix, but is there any magic that
  can be done to remove the old directories at boot rather than waiting
  for the directory to "expire" again? Is it possible to avoid the
  modification time being updated?

  Simply removing the whole directory based on its creation or
  modification times, without first checking its contents for newer
  files, would probably not be preferable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Thu Jan 29 15:13:27 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1415974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1415974] Re: Cleaning a directory in /tmp during boot updates the directory's modification time

2015-01-29 Thread Ken Sharp
** Summary changed:

- Cleaning a directory in /tmp during boot updates the folder's modification 
time
+ Cleaning a directory in /tmp during boot updates the directory's modification 
time

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

Title:
  Cleaning a directory in /tmp during boot updates the directory's
  modification time

Status in sysvinit package in Ubuntu:
  New

Bug description:
  When set to anything other than 0 (clean all of /tmp), /tmp is cleaned
  of "old" files, but in doing so it updates the modification times of
  all the directories, so that they remain until they themselves become
  "old".

  I hope this makes sense, an example:

  During boot files in /tmp older than three days will be cleaned.
  Files in /tmp/olddir will be cleaned.
  /tmp/olddir will have its modification time updated, it is no longer an old 
directory.
  /tmp/olddir is left behind because it is not recognised as an old directory.

  It's minor and may be impossible to fix, but is there any magic that
  can be done to remove the old directories at boot rather than waiting
  for the directory to "expire" again? Is it possible to avoid the
  modification time being updated?

  Simply removing the whole directory based on its creation or
  modification times, without first checking its contents for newer
  files, would probably not be preferable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Thu Jan 29 15:13:27 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1415974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp