the file.
>
> However, thank you for the suggestion, which I shall retain for future
> consideration.
>
>
If you do not want it to disappear altogether, you can just prune it. I
have this in my ¨/home//.bash_profile¨ file:
# prune the ~/.xsession-errors file if it grows beyond 1M
On 15/09/2014, Chen Wei wrote:
> On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
>> .xsession-errors, which is currently sitting at about 740MB, and has
>> been growing in the last hour.
>>
>> entries from before the current boot session) entries, so as to reduce
>> the file size to co
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
> .xsession-errors, which is currently sitting at about 740MB, and has
> been growing in the last hour.
>
> entries from before the current boot session) entries, so as to reduce
> the file size to content that is necessary to retain for
Bret Busby writes:
> So, I believe (unttil and unless, advised otherwise) that the
> deleteing the file (which did not free up the disc space, in itself),
> and then, renaming the xsystem-errors.old file, to xsystem-errors,
> appears to have disappeared the problem, which, if I had known
> earlie
Bret Busby writes:
> I note that, with that file that is being accessed by Nautilus,
> assuming that the number 1169162 , is the size of the file, I have
> tried, but, apparently, can not reduce that to zero, as that number
> does not change, with my attempts.
On a side note: You could try nemo
On Wed, 10 Sep 2014, Bret Busby wrote:
On 10/09/2014, david...@ling.ohio-state.edu wrote:
On Tue, 9 Sep 2014, Jonathan Dowland wrote:
On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote:
The file has (kind of) gone, now (it is no longer accessible, but,
appears to still exist, in the
On 10/09/2014, david...@ling.ohio-state.edu
wrote:
> On Tue, 9 Sep 2014, Jonathan Dowland wrote:
>
>> On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote:
>>> The file has (kind of) gone, now (it is no longer accessible, but,
>>> appears to still exist, in the ether of the unknown; still ta
On 10/09/2014, Chris Bannister wrote:
> On Wed, Sep 10, 2014 at 12:36:42AM +0800, Bret Busby wrote:
>> Before seeing the above message, after someone previously saying that
>> deleting the file would not cause any (extra) problems, but would not
>> free up disc space, I deleted the file, then ran
On Tue, 9 Sep 2014, Jonathan Dowland wrote:
On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote:
The file has (kind of) gone, now (it is no longer accessible, but,
appears to still exist, in the ether of the unknown; still taking up
disc space, whilst, in theory, non-existent),
A file
On Wed, Sep 10, 2014 at 12:36:42AM +0800, Bret Busby wrote:
> Before seeing the above message, after someone previously saying that
> deleting the file would not cause any (extra) problems, but would not
> free up disc space, I deleted the file, then ran "Empty Trash Can",
> but, no disc space was
On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote:
> The file has (kind of) gone, now (it is no longer accessible, but,
> appears to still exist, in the ether of the unknown; still taking up
> disc space, whilst, in theory, non-existent),
A file continues to use up disk space until all op
On 10/09/2014, Brian wrote:
> On Wed 10 Sep 2014 at 01:24:24 +0800, Bret Busby wrote:
>
>> Just out of interest, "top" shows the system as having been up for 21
>> days, so, the xsession-errors file grew to 743MB, in 21 days. I saw,
>> at the top of that file, be
On Wed 10 Sep 2014 at 01:24:24 +0800, Bret Busby wrote:
> Just out of interest, "top" shows the system as having been up for 21
> days, so, the xsession-errors file grew to 743MB, in 21 days. I saw,
> at the top of that file, before I deleted it, reference to 21 August,
> s
ailable, so the
> system required rebooting every couple of weeks or so (a bit like
> Win95, I think it was, but, I believe that Win95 generally lasted for
> about four weeks, before needing rebooting), or, it simply crashed.
>
>
Just out of interest, "top" shows t
On 09/09/2014, Chris Bannister wrote:
> On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
>> Hello.
>>
>> I am concerned that, should I simply delete the file, the system will
>> crash or otherwise damage to the boot session, would occur.
>
> I very much doubt that any such damage would
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
> Hello.
>
> I am concerned that, should I simply delete the file, the system will
> crash or otherwise damage to the boot session, would occur.
I very much doubt that any such damage would occur by deleting it, but
the following incanta
On 09/09/14 at 03:29pm, Bret Busby wrote:
> Hello.
>
> In trying to work out why my disk space gets progressively consumed so
> that I repeatedly run out of disc space without any known reason, in
> examining my hidden files in my home directory, I found the file
> .xsession-errors, which is curre
Hi.
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
> Does some uttility or command (with switches) exist, that can purge
> the file of redundant (for example, entries over a week old, or,
> entries from before the current boot session) entries, so as to reduce
> the file size to cont
Hello.
In trying to work out why my disk space gets progressively consumed so
that I repeatedly run out of disc space without any known reason, in
examining my hidden files in my home directory, I found the file
.xsession-errors, which is currently sitting at about 740MB, and has
been growing in t
On Thursday 20 May 2010 23:38:42 T o n g wrote:
> On Wed, 19 May 2010 11:33:02 -0500, Boyd Stephen Smith Jr. wrote:
> >> I took a look, the reason and cure is very simple -- having X to trunk
> >> it each time when started
> >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287876) whereas
> >>
On Wed, 19 May 2010 11:33:02 -0500, Boyd Stephen Smith Jr. wrote:
>> I took a look, the reason and cure is very simple -- having X to trunk
>> it each time when started
>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287876) whereas
>> currently, my ~/.xsession-errors kept logs back to stone
On 2010-05-19 19:19 +0200, d.sastre.med...@gmail.com wrote:
> FWIW, I don't have that problem, although /etc/X11/Xsession says:
>
> exec >>"$ERRFILE" 2>&1 (despite the solution proposed in¹)
> echo "$PROGNAME: X session started for $LOGNAME at $(date)"
>
> and the contents of it are, unsurprisingl
T o n g wrote:
Hi,
I am astonished to find out that my ~/.xsession-errors grows to a
humongous 640M! My wife's is nearly 400M as well. This is way way too
big.
I took a look, the reason and cure is very simple -- having X to trunk it
each time when started
(http://bugs.debian.org/cgi-bin/b
On Wed, May 19, 2010 at 06:45:04PM +0200, Sven Joachim wrote:
> On 2010-05-19 18:18 +0200, T o n g wrote:
>
> > I am astonished to find out that my ~/.xsession-errors grows to a
> > humongous 640M! My wife's is nearly 400M as well. This is way way too
> > big.
> >
> > I took a look, the reason
On 2010-05-19 18:18 +0200, T o n g wrote:
> I am astonished to find out that my ~/.xsession-errors grows to a
> humongous 640M! My wife's is nearly 400M as well. This is way way too
> big.
>
> I took a look, the reason and cure is very simple -- having X to trunk it
> each time when started
>
On Wednesday 19 May 2010 11:18:57 T o n g wrote:
> I am astonished to find out that my ~/.xsession-errors grows to a
> humongous 640M! My wife's is nearly 400M as well. This is way way too
> big.
>
> I took a look, the reason and cure is very simple -- having X to trunk it
> each time when started
Hi,
I am astonished to find out that my ~/.xsession-errors grows to a
humongous 640M! My wife's is nearly 400M as well. This is way way too
big.
I took a look, the reason and cure is very simple -- having X to trunk it
each time when started
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
I found a nice discussion of this issue on a ubuntu forum.
https://bugs.launchpad.net/ubuntu/dapper/+source/xinit/+bug/60448
they discuss various approaches to handling the problem.
They point out that gdm wipes out the log on restart.
I am not running gdm, i start X with startx,
that is why s
Hi,
I wanted to claim the all time maximum size for the .xsession-errors file.
My home partition has a raid1 of 2 400G hard drives. Just today my home
partition became 100% full.
I see that this was already discussed last year on debian-user so I just post
it to let people know
who will come
I'm running LTSP (Thin clients), on Woody, and recently my most popular
application, The Gimp, started to cause huge .xsession-errors files, the file would
grow until it took 100% of the partition in a mather of minutes. The files contains
millions of identical lines:
"gimp segmentation fa
on Fri, Oct 05, 2001 at 09:06:21AM -0700, Sean 'Shaleh' Perry ([EMAIL
PROTECTED]) wrote:
>
> On 05-Oct-2001 David Purton wrote:
> > at some point in the last day or so my .xsession-erros fil grew to an
> > enormous size and completely filled up my hard disk (like almost 1GB in
> > size).
> >
> >
This happened to me, too. I reported some weird jumps in the % usage
reported by df, and subsequently found that this file had mushroomed at
some point (the other % were addressed by running apt-get clean).
Glenn Becker
On Sat, 6
Oct 2001, David Purton wrote:
> at some point in the last day or
On 05-Oct-2001 David Purton wrote:
> at some point in the last day or so my .xsession-erros fil grew to an
> enormous size and completely filled up my hard disk (like almost 1GB in
> size).
>
> it seemed to contain binary junk, but I've delete it now (needed to
> download my mail :) )
>
> what
at some point in the last day or so my .xsession-erros fil grew to an
enormous size and completely filled up my hard disk (like almost 1GB in
size).
it seemed to contain binary junk, but I've delete it now (needed to
download my mail :) )
what would cause this?
cheers
dc
-
Hi,
I'm using Windowmaker from potato, and lately I've noticed my
.xsession-errors file consists of seeming endless lines of
heyho!
It's really getting annoying. After a couple of hours this afternoon,
it was over 6M in size. Where the heck is it coming from, and how
d
35 matches
Mail list logo
