Hi,
I join too late but ... (I do not use tmpfs for /tmp)
On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
I'm running an updated wheezy and today faced with this little
problematic.
(...)
Okay, so /tmp is full. Fine. I
On Sun, 04 Mar 2012 18:12:09 +0900, Osamu Aoki wrote:
Hi,
I join too late but ... (I do not use tmpfs for /tmp)
Time does not matter when good feedback comes to place :-)
On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
I'm
I stop using huge tmpfs for tmp since it gains nothing for me.
Okay, so no more worries about this. I will keep the old-good default for
/tmp then.
Greetings,
I also got in problems, when k3b asked me for a temporary place for a
temporary ISO. I choose /tmp (good choice for normal
On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
I think it would have been nice to have a warning of this change of
behaviour. I have apt-listchanges installed and I'm sure it didn't
notify me of any changes.
True, but there was a discussion on debian-devel titled:
/tmp as tmpfs and
On Thu, Mar 01, 2012 at 02:54:30AM +1300, Chris Bannister wrote:
On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
I think it would have been nice to have a warning of this change of
behaviour. I have apt-listchanges installed and I'm sure it didn't
notify me of any changes.
True, but
On 22/02/12 01:10, Seb wrote:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on
Dom wrote:
I think it would have been nice to have a warning of this change of
behaviour. I have apt-listchanges installed and I'm sure it didn't
notify me of any changes.
These types of changes are discussed in debian-devel. In a released
system they would be in the release notes. But since
On Mon, 28 Nov 2011 19:44:46 +,
Dom to...@rpdom.net wrote:
On 28/11/11 18:07, Camaleón wrote:
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression
for browsing the archive) the kernel
Seb wrote:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on /?
Set RAMTMP=no
On Tue, 21 Feb 2012 18:17:15 -0700,
Bob Proulx b...@proulx.com wrote:
Seb wrote:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
Seb writes:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on /?
Set TEMPDIR
John Hasler wrote:
Seb writes:
I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp. What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is
Seb wrote:
Bob Proulx wrote:
Set RAMTMP=no in the /etc/default/rcS file.
# sed --in-place 's/RAMTMP=.*/RAMTMP=no/' /etc/default/rcS
Thank you! With this modification, does /tmp still get cleared after
each reboot?
Yes. That is controlled by TMPTIME=0 in the same /etc/default/rcS
Bob writes:
Did you mean TMPDIR?
Yes. Note that you may want to provide for cleanup. Consider tmpreaper.
Although not every program is coded to honor TMPDIR...
File bug reports.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Tue, 21 Feb 2012 19:55:36 -0700,
Bob Proulx b...@proulx.com wrote:
John Hasler wrote:
Seb writes: I just discovered to my horror /tmp is handled by a
tmpfs system that allocates by default a percentage of RAM that
happens to be too small for my use of /tmp. What is the Debianish
way
John Hasler wrote:
Bob writes:
Did you mean TMPDIR?
Yes. Note that you may want to provide for cleanup. Consider tmpreaper.
I like tmpreaper quite a bit. It is great for /tmp and /var/tmp. For
$HOME/tmp I don't think it is needed. For $HOME/tmp just running find
$HOME/tmp with some
On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
I'm running an updated wheezy and today faced with this little
problematic.
(...)
Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
more situations like this in the future so some questions arise. As the
current tmpfs
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:
http://picpaste.com/mc-error-YXdyRawO.gif
My
On 28/11/11 19:07, Camaleón wrote:
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:
Camaleón wrote:
/dev/sda2247G 7,7G 239G 4% /
tmpfs423M 423M 0 100% /tmp --- here!
Okay, so /tmp is full. Fine. ...
Especially when you have 250G of space it seems egregious to clamp it
down to only 423M.
1/ How many room should be set for a /tmp
On 28/11/11 18:07, Camaleón wrote:
Hello,
I'm running an updated wheezy and today faced with this little
problematic.
While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:
21 matches
Mail list logo
