Am 06.03.2013 10:31, schrieb Ed Greshko:
> On 03/06/13 17:20, Reindl Harald wrote:
>>
>> Am 06.03.2013 10:03, schrieb Ed Greshko:
>>> On 03/06/13 16:52, Gabriel VLASIU wrote:
On Wed, 6 Mar 2013, Ed Greshko wrote:
> So you feel the -u parameter (access time) isn't sufficient to keep
On 03/06/13 17:20, Reindl Harald wrote:
>
> Am 06.03.2013 10:03, schrieb Ed Greshko:
>> On 03/06/13 16:52, Gabriel VLASIU wrote:
>>> On Wed, 6 Mar 2013, Ed Greshko wrote:
>>>
So you feel the -u parameter (access time) isn't sufficient to keep from
deleting directories in use?
>>> If the s
Am 06.03.2013 10:03, schrieb Ed Greshko:
> On 03/06/13 16:52, Gabriel VLASIU wrote:
>> On Wed, 6 Mar 2013, Ed Greshko wrote:
>>
>>> So you feel the -u parameter (access time) isn't sufficient to keep from
>>> deleting directories in use?
>> If the service did not access the private tmp directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 6 Mar 2013, Ed Greshko wrote:
> I see nothing in that bugzilla which states that a service has failed
> due to a directory in /var/tmp/systemd-private-* being deleted by the
> cron job while the file/directory was in use.
I did not say tha
On 03/06/13 16:52, Gabriel VLASIU wrote:
> On Wed, 6 Mar 2013, Ed Greshko wrote:
>
> > So you feel the -u parameter (access time) isn't sufficient to keep from
> > deleting directories in use?
> If the service did not access the private tmp directory in X day, yes.
>
> https://bugzilla.redhat.com/s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 6 Mar 2013, Ed Greshko wrote:
> So you feel the -u parameter (access time) isn't sufficient to keep from
> deleting directories in use?
If the service did not access the private tmp directory in X day, yes.
https://bugzilla.redhat.com/show
On 03/06/13 16:17, Gabriel VLASIU wrote:
> On Wed, 6 Mar 2013, Ed Greshko wrote:
>
> > Anything wrong with letting the system clean up its mess like that on a
> > regular basis?
> Yes, is wrong!
> If any of your services run for more than 5 days, the private tmp
> directories are removed. Which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 6 Mar 2013, Ed Greshko wrote:
> Anything wrong with letting the system clean up its mess like that on a
> regular basis?
Yes, is wrong!
If any of your services run for more than 5 days, the private tmp
directories are removed. Which is wro
On Wed, 06 Mar 2013 10:00:05 +0200
Cristian Sava wrote:
> The problem is that they still are there (like here
> https://bugzilla.redhat.com/show_bug.cgi?id=801943 )
> Do you expect any user to delete or fix himself?
>
> C. Sava
>
>
If you don't want to wait for the system to clean itself.
or m
On Wed, 2013-03-06 at 15:47 +0800, Ed Greshko wrote:
> On 03/06/13 15:25, Cristian Sava wrote:
> > Why /var/log/tmp looks like this and systemd-private dirs are never
> > automatically deleted, even at reboot?
> >
> > [root@localhost tmp]# ls -l
> > total 796
> > drwx--. 2 fx fx 4096
On 03/06/13 16:00, Cristian Sava wrote:
> The problem is that they still are there (like here
> https://bugzilla.redhat.com/show_bug.cgi?id=801943 )
> Do you expect any user to delete or fix himself?
But, they eventually are deleted.
[egreshko@meimei ~]$ cd /var/tmp
[egreshko@meimei tmp]$ ll
On Wed, 2013-03-06 at 15:47 +0800, Ed Greshko wrote:
> On 03/06/13 15:25, Cristian Sava wrote:
> > Why /var/log/tmp looks like this and systemd-private dirs are never
> > automatically deleted, even at reboot?
> >
> > [root@localhost tmp]# ls -l
> > total 796
> > drwx--. 2 fx fx 4096
On 03/06/13 15:25, Cristian Sava wrote:
> Why /var/log/tmp looks like this and systemd-private dirs are never
> automatically deleted, even at reboot?
>
> [root@localhost tmp]# ls -l
> total 796
> drwx--. 2 fx fx 4096 Feb 28 13:43 kdecache-fx
> drwx--. 2 fx fx 4096 F
Why /var/log/tmp looks like this and systemd-private dirs are never
automatically deleted, even at reboot?
[root@localhost tmp]# ls -l
total 796
drwx--. 2 fx fx 4096 Feb 28 13:43 kdecache-fx
drwx--. 2 fx fx 4096 Feb 15 14:37 plugtmp-1
-rw---. 1 akmods akmods 1
14 matches
Mail list logo
