On 01/12/11 07:49, "Jérôme M. Berger" wrote:
> Leonid Isaev wrote:
>> Hibernating is a purely windows concept, doing it on a linux machine is
>> basically looking for trouble, especially because hibernation gives no
>> benefits
>> over shutting down.
>
> I never reboot my laptop unless I j
Leonid Isaev wrote:
> On Tue, 29 Nov 2011 19:50:46 +0100
> "Jérôme M. Berger" wrote:
>> And if your machine only boots very rarely (because it runs
>> continuously or because you hibernate it instead of rebooting) then
>> your "temporary" folder is never cleaned up. The solution that makes
>>
On 11/29/2011 05:20 PM, clemens fischer wrote:
With tmpwatch one gets to choose files not accessed or modified for
a certain period, and it needs no config file. Arch-tmpfiles, OTOH,
would require such a thing.
Then again, a simple "find -atime + -exec /bin/rm
'{}' +" does about the same as t
Tom Gundersen wrote:
> 2011/11/29 "Jérôme M. Berger" :
>
>> And if your machine only boots very rarely (because it runs
>> continuously or because you hibernate it instead of rebooting) then
>> your "temporary" folder is never cleaned up. The solution that makes
>> the most sense is to have
On Tue, 29 Nov 2011 19:50:46 +0100
"Jérôme M. Berger" wrote:
> And if your machine only boots very rarely (because it runs
> continuously or because you hibernate it instead of rebooting) then
> your "temporary" folder is never cleaned up. The solution that makes
> the most sense is to have
2011/11/29 "Jérôme M. Berger" :
> David Rosenstrauch wrote:
>> On 11/25/2011 11:55 AM, Leonid Isaev wrote:
>>> Actually, what is stupid is keeping /tmp in RAM. It is an important
>>> dir, where
>>> you might have an valuable info in case of a system crash. I could never
>>> understand the logic beh
David Rosenstrauch wrote:
> On 11/25/2011 11:55 AM, Leonid Isaev wrote:
>> Actually, what is stupid is keeping /tmp in RAM. It is an important
>> dir, where
>> you might have an valuable info in case of a system crash. I could never
>> understand the logic behind this choice.
>
> Actually, I think
On 28 November 2011 18:04, David Rosenstrauch wrote:
> On 11/25/2011 11:55 AM, Leonid Isaev wrote:
>
>> Actually, what is stupid is keeping /tmp in RAM. It is an important dir,
>> where
>> you might have an valuable info in case of a system crash. I could never
>> understand the logic behind this
On 11/25/2011 11:55 AM, Leonid Isaev wrote:
Actually, what is stupid is keeping /tmp in RAM. It is an important dir, where
you might have an valuable info in case of a system crash. I could never
understand the logic behind this choice.
Actually, I think it makes a lot of sense. It lets you tr
Myra Nelson wrote:
> The .install files are contained in the package.
I know. I wanted to know where they go before the entire package with
all transactions is considered "done". The warning indicated that the
first, preliminary extraction step went wrong.
> Might I ask what you were compiling
On Fri, Nov 25, 2011 at 4:32 AM, Mauro Santos
wrote:
> On 25-11-2011 07:46, C Anthony Risinger wrote:
>>
>> ... however, i would consider it a bug for applications to
>> store *very* large files (exceeding 50-100M or so) in /tmp -- /var/tmp
>> would be more appropriate, even for ephemeral/transie
On 26/11/11 02:40, clemens fischer wrote:
Gaetan Bisson wrote:
If that's easy then it shouldn't be too hard for you to open a bug
report on the tracker and submit a patch.
Then what component does the actual extracting? Is it libfetch? That
would be an upstream moving target, because it com
On 26/11/11 02:35, clemens fischer wrote:
Allan McRae wrote:
On 25/11/11 09:18, clemens fischer wrote:
would it be possible to let pacman, libalpm and libfetch honor the
environment variable TMPDIR?
File a bug report or at least post to the pacman-dev list. Then
relevant people might actua
On Fri, Nov 25, 2011 at 12:42, clemens fischer <
ino-n...@spotteswoode.dnsalias.org> wrote:
> clemens fischer wrote:
>
> > Gaetan Bisson wrote:
> >
> >> If that's easy then it shouldn't be too hard for you to open a bug
> >> report on the tracker and submit a patch.
> >
> > Then what component doe
clemens fischer wrote:
> Gaetan Bisson wrote:
>
>> If that's easy then it shouldn't be too hard for you to open a bug
>> report on the tracker and submit a patch.
>
> Then what component does the actual extracting? Is it libfetch? That
> would be an upstream moving target, because it comes fro
On Fri, 25 Nov 2011 18:57:22 +0100
Tom Gundersen wrote:
> On Fri, Nov 25, 2011 at 6:31 PM, Leonid Isaev wrote:
> > On Fri, 25 Nov 2011 18:07:18 +0100
> > Geert Hendrickx wrote:
> >
> >> On Fri, Nov 25, 2011 at 10:55:55 -0600, Leonid Isaev wrote:
> >> > Actually, what is stupid is keeping /tmp i
Leonid Isaev wrote:
> On Fri, 25 Nov 2011 18:07:18 +0100
> Geert Hendrickx <...> wrote:
>
>> On Fri, Nov 25, 2011 at 10:55:55 -0600, Leonid Isaev wrote:
>>
>> > Actually, what is stupid is keeping /tmp in RAM. It is an important
>> > dir, where you might have an valuable info in case of a system
On Fri, Nov 25, 2011 at 6:31 PM, Leonid Isaev wrote:
> On Fri, 25 Nov 2011 18:07:18 +0100
> Geert Hendrickx wrote:
>
>> On Fri, Nov 25, 2011 at 10:55:55 -0600, Leonid Isaev wrote:
>> > Actually, what is stupid is keeping /tmp in RAM. It is an important dir,
>> > where you might have an valuable i
On Fri, 25 Nov 2011 18:07:18 +0100
Geert Hendrickx wrote:
> On Fri, Nov 25, 2011 at 10:55:55 -0600, Leonid Isaev wrote:
> > Actually, what is stupid is keeping /tmp in RAM. It is an important dir,
> > where you might have an valuable info in case of a system crash. I could
> > never understand th
On Fri, Nov 25, 2011 at 10:55:55 -0600, Leonid Isaev wrote:
> Actually, what is stupid is keeping /tmp in RAM. It is an important dir,
> where you might have an valuable info in case of a system crash. I could
> never understand the logic behind this choice.
Reducing disk i/o.
Geert
On Fri, 25 Nov 2011 00:18:43 +0100
clemens fischer wrote:
> Hi,
>
> would it be possible to let pacman, libalpm and libfetch honor the
> environment variable TMPDIR?
>
> I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and
> make it big enough, but not too big, as it takes awa
Allan McRae wrote:
> On 25/11/11 09:18, clemens fischer wrote:
>
>> would it be possible to let pacman, libalpm and libfetch honor the
>> environment variable TMPDIR?
>
> File a bug report or at least post to the pacman-dev list. Then
> relevant people might actually see your request.
I'm not "r
Gaetan Bisson wrote:
> If that's easy then it shouldn't be too hard for you to open a bug
> report on the tracker and submit a patch.
Then what component does the actual extracting? Is it libfetch? That
would be an upstream moving target, because it comes from netbsd. Do
you guys accept patche
On 25-11-2011 07:46, C Anthony Risinger wrote:
> ... however, i would consider it a bug for applications to
> store *very* large files (exceeding 50-100M or so) in /tmp -- /var/tmp
> would be more appropriate, even for ephemeral/transient files -- idk
Just out of curiosity, why do you say that? I
On Fri, Nov 25, 2011 at 7:04 AM, Hector Martinez-Seara wrote:
> Sometimes you simply need more space that the one available in /tmp.
> In all my systems /tmp is in ram and as some machines have only 4Gb
> memory the available space in /tmp is about 2Gb only which is
> sufficient for most of the
On Thu, Nov 24, 2011 at 5:18 PM, clemens fischer
wrote:
>
> I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and
> make it big enough, but not too big, as it takes away RAM when getting
> loaded.
there isn't much reason to limit tmpfs or /tmp ... you should be using
a swap devic
Hi,
Sometimes you simply need more space that the one available in /tmp.
In all my systems /tmp is in ram and as some machines have only 4Gb
memory the available space in /tmp is about 2Gb only which is
sufficient for most of the stuff but some compilations need more.
Hector
On 25 November 2011
On 25/11/11 09:18, clemens fischer wrote:
Hi,
would it be possible to let pacman, libalpm and libfetch honor the
environment variable TMPDIR?
I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and
make it big enough, but not too big, as it takes away RAM when getting
loaded.
[2011-11-25 00:18:43 +0100] clemens fischer:
> would it be possible to let pacman, libalpm and libfetch honor the
> environment variable TMPDIR?
>
> I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and
> make it big enough, but not too big, as it takes away RAM when getting
> loa
Hi,
would it be possible to let pacman, libalpm and libfetch honor the
environment variable TMPDIR?
I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and
make it big enough, but not too big, as it takes away RAM when getting
loaded.
#define TMP_LOC "TMPDIR"
#include /* gete
30 matches
Mail list logo
