Re: Weird warning from console-kit-daemon

2012-05-13 Thread Sébastien Kalt 
Hi,

2012/5/10 Curt :
> On 2012-05-06, Sébastien Kalt  wrote:
>>
>> Thank you for your answer, but I still think physical hard drive space is
>> not the problem.
>
> How about inodes?
>
> df -i
$ df -i
Filesystem                                              Inodes  IUsed
 IFree IUse% Mounted on
rootfs                                                 248 707714
9291534    8% /
udev                                                    497175    447
496728    1% /dev
tmpfs                                                   498668    401
498267    1% /run
/dev/disk/by-uuid/d30adeed-998c-4f8b-b25c-185113da1cda 248 707714
9291534    8% /
tmpfs                                                   498668      4
498664    1% /run/lock
tmpfs                                                   498668     37
498631    1% /tmp
tmpfs                                                   498668      5
498663    1% /run/shm

Doesn't seem to be full ;)

Camaleón wrote :
> Yes. Hum, okay, the let's go back to the original idea of enabling them
> and see how it goes (append "cgroup_enable=memory" to the kernel line) :-)
I tried it, and I have the same messages :

$ dmesg |grep "Command line"
[    0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=d30adeed-998c-4f8b-b25c-185113da1cda ro quiet
cgroup_enable=memory

$ cat /proc/cgroups
#subsys_name hierarchy num_cgroups enabled
cpuset 0 1 1
cpu 0 1 1
cpuacct 0 1 1
memory 0 1 1
devices 0 1 1
freezer 0 1 1
net_cls 0 1 1
blkio 0 1 1
perf_event 0 1 1

$ tail /var/log/syslog
May 13 16:00:57 crapaud64 console-kit-daemon[2289]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
May 13 16:01:27 crapaud64 console-kit-daemon[2289]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
May 13 16:01:57 crapaud64 console-kit-daemon[2289]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
May 13 16:02:27 crapaud64 console-kit-daemon[2289]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
May 13 16:02:57 crapaud64 console-kit-daemon[2289]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device

So I'll file a bug, as soon as I have enough time ;)

Thank you for your help.

Sebastien


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/can64bfyi0crg3rkgxzl-lpl38w1xca7kbu8syatdvc2rvet...@mail.gmail.com

Re: Weird warning from console-kit-daemon

2012-05-10 Thread Curt 
On 2012-05-06, Sébastien Kalt  wrote:
>
> Thank you for your answer, but I still think physical hard drive space is
> not the problem.

How about inodes?

df -i


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjqnlie.2o7.cu...@einstein.electron.org

Re: Weird warning from console-kit-daemon

2012-05-09 Thread Camaleón 
On Wed, 09 May 2012 19:54:34 +0200, Sébastien Kalt wrote:

> Finally it seems my laptop took a holiday yesterday, just like me ;)
> 
> Today the messages are back.

Ouch.

> $  cat /proc/cgroups
> #subsys_name  hierarchy   num_cgroups enabled 
> cpuset0   1   1
> cpu   0   1   1
> cpuacct   0   1   1
> memory0   1   0
> devices   0   1   1
> freezer   0   1   1
> net_cls   0   1   1
> blkio 0   1   1
> perf_event0   1   1

Yes, that's the same I get which seems to indicate it's disabled for 
memory ("0").

> So memory has enabled at 0, so I guess it's really disabled.

Yes. Hum, okay, the let's go back to the original idea of enabling them 
and see how it goes (append "cgroup_enable=memory" to the kernel line) :-)

> Do you have any other ideas, if it's not coming from cgroup ?
> 
> Is there another place / mailing list to ask that question ?

To be sincere, I can't guess what's the source that generates that 
"console-kit-daemon" messages, but being a "warning" and not an "error" 
it could have no additional side effects. Despite the messages, are you 
experiencing any noticeable problem?

Anyway, given that you're running sid maybe is worth opening a bug report 
against "consolekit" package :-?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/joekg1$bci$2...@dough.gmane.org

Re: Weird warning from console-kit-daemon

2012-05-09 Thread Sébastien Kalt 
Hi,

Finally it seems my laptop took a holiday yesterday, just like me ;)

Today the messages are back.

$  cat /proc/cgroups
#subsys_namehierarchy   num_cgroups enabled
cpuset  0   1   1
cpu 0   1   1
cpuacct 0   1   1
memory  0   1   0
devices 0   1   1
freezer 0   1   1
net_cls 0   1   1
blkio   0   1   1
perf_event  0   1   1

So memory has enabled at 0, so I guess it's really disabled.

Do you have any other ideas, if it's not coming from cgroup ?

Is there another place / mailing list to ask that question ?

Sebastien


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/can64bfbwlgarw671frdob41ekpgkfybs79ptleq6k21avo+...@mail.gmail.com

Re: Weird warning from console-kit-daemon

2012-05-09 Thread Camaleón 
On Tue, 08 May 2012 21:05:34 +0200, Sébastien Kalt wrote:

> 2012/5/8 Camaleón :
>> On Mon, 07 May 2012 20:49:32 +0200, Sébastien Kalt wrote:
>>> Is cgroup memory really disabled ?
>>
>> I can't tell, it doesn't seem to be so (I would have expected a message
>> saying it has been disabled) though it should, or at least that's what
>> the docs say :-?

> cat /proc/cgroup will tell you which cgroup is enabled.

I get none under "enabled" column despite dmesg message :-?

>> Are the above errors coming up when you are locally logged or when
>> running from a remote system or when some specific configuration is in
>> place (e.g., it happens when running an X session or launching a GUI
>> application but does not when no X server is in place)?

> It happens when I log in an X session, and then a console, and/or launch
> an application as another user with gksu, or su to another user in an
> urxvt console.
>
> But, weirdly, the messages stopped at 14h41 today, just after my last
> synaptic update !
> 
> Here are the updated packages :

(...)

> I'll confirm tomorrow that the messages have definitely disappeared ;)

Okay :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/joe0lq$bci$5...@dough.gmane.org

Re: Weird warning from console-kit-daemon

2012-05-08 Thread Sébastien Kalt 
Hi,

2012/5/8 Camaleón :
> On Mon, 07 May 2012 20:49:32 +0200, Sébastien Kalt wrote:
>> Is cgroup memory really disabled ?
>
> I can't tell, it doesn't seem to be so (I would have expected a
> message saying it has been disabled) though it should, or at least
> that's what the docs say :-?
cat /proc/cgroup will tell you which cgroup is enabled.

> 1/ Cgroup is still enabled for memory handling.
> 2/ The printed mesages have no relation with this cgroup thingy :-)
>
> Are the above errors coming up when you are locally logged or when
> running from a remote system or when some specific configuration is
> in place (e.g., it happens when running an X session or launching a
> GUI application but does not when no X server is in place)?
It happens when I log in an X session, and then a console, and/or
launch an application as another user with gksu, or su to another user
in an urxvt console.

But, weirdly, the messages stopped at 14h41 today, just after my last
synaptic update !

Here are the updated packages :

coreutils:amd64 (8.13-3.1, 8.13-3.2),
python-qt4:amd64 (4.9.1-1, 4.9.1-3),
ufraw-batch:amd64 (0.18-1.1+b1, 0.18-1.1+b2),
cpp:amd64 (4.6.3-5, 4.7.0-6),
gcc:amd64 (4.6.3-5, 4.7.0-6),
python-pyexiv2:amd64 (0.3.2-1+b1, 0.3.2-1+b2),
pciutils:amd64 (3.1.9-2, 3.1.9-3),
gdal-bin:amd64 (1.7.3-6+b4, 1.9.0-1),
libdbd-mysql-perl:amd64 (4.020-1+b1, 4.021-1),
libvorbisfile3:amd64 (1.3.2-1.2, 1.3.2-1.3),
lsb-base:amd64 (4.1+Debian2, 4.1+Debian3),
libvorbisenc2:amd64 (1.3.2-1.2, 1.3.2-1.3),
sox:amd64 (14.4.0-2, 14.4.0-3),
mysql-client:amd64 (5.1.62-1, 5.5.23-2),
libperl5.14:amd64 (5.14.2-9, 5.14.2-10),
python-gdal:amd64 (1.7.3-6+b4, 1.9.0-1),
grep:amd64 (2.11-3, 2.12-1),
libevent-2.0-5:amd64 (2.0.18-stable-1, 2.0.19-stable-1),
libvorbis0a:amd64 (1.3.2-1.2, 1.3.2-1.3),
libfolks-telepathy25:amd64 (0.6.8-2, 0.6.9-1),
perl-doc:amd64 (5.14.2-9, 5.14.2-10),
libio-socket-ssl-perl:amd64 (1.66-1, 1.67-1),
mysql-common:amd64 (5.1.62-1, 5.5.23-2),
lsb-release:amd64 (4.1+Debian2, 4.1+Debian3),
libogg0:amd64 (1.2.2~dfsg-1, 1.2.2~dfsg-1.1)
Remove: mysql-server-core-5.1:amd64 (5.1.62-1),
mysql-server-5.1:amd64 (5.1.62-1),
mysql-client-5.1:amd64 (5.1.62-1)

I'll confirm tomorrow that the messages have definitely disappeared ;)

Sebastien


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/can64bfamzzbqxwvffxemdbcop4kloj4k-m2mcx2cijwcomw...@mail.gmail.com

Re: Weird warning from console-kit-daemon

2012-05-08 Thread Camaleón 
On Mon, 07 May 2012 20:49:32 +0200, Sébastien Kalt wrote:

> I've launched my kernel with cgroup_disable=memory :
> 
> [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 
> root=UUID=d30adeed-998c-4f8b-b25c-185113da1cda ro cgroup_disable=memory
> 
> Later in dmesg I have thoses lines :
> 
> [0.010561] Initializing cgroup subsys cpuacct 
> [0.010657] Initializing cgroup subsys memory 
> [0.010762] Initializing cgroup subsys devices 
> [0.010855] Initializing cgroup subsys freezer 
> [0.010953] Initializing cgroup subsys net_cls 
> [0.011045] Initializing cgroup subsys blkio 
> [0.011156] Initializing cgroup subsys perf_event

I also get those lines with no extra parameter added.

> Is cgroup memory really disabled ?

I can't tell, it doesn't seem to be so (I would have expected a 
message saying it has been disabled) though it should, or at least 
that's what the docs say :-?

> Anyway, I still have the same messages :
> 
> May  7 20:06:48 crapaud64 console-kit-daemon[2468]: WARNING: Failed to add 
> monitor on '/dev/pts/2': No space left on device 
> May  7 20:07:04 crapaud64 console-kit-daemon[2468]: WARNING: Failed to add 
> monitor on '/dev/tty1': No space left on device

We are still at the same place. It can be because:

1/ Cgroup is still enabled for memory handling.
2/ The printed mesages have no relation with this cgroup thingy :-)

Are the above errors coming up when you are locally logged or when 
running from a remote system or when some specific configuration is 
in place (e.g., it happens when running an X session or launching a 
GUI application but does not when no X server is in place)?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jobcr2$vio$6...@dough.gmane.org

Re: Weird warning from console-kit-daemon

2012-05-07 Thread Sébastien Kalt 
Hi,

I've launched my kernel with cgroup_disable=memory :

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=d30adeed-998c-4f8b-b25c-185113da1cda ro
cgroup_disable=memory

Later in dmesg I have thoses lines :

[0.010561] Initializing cgroup subsys cpuacct
[0.010657] Initializing cgroup subsys memory
[0.010762] Initializing cgroup subsys devices
[0.010855] Initializing cgroup subsys freezer
[0.010953] Initializing cgroup subsys net_cls
[0.011045] Initializing cgroup subsys blkio
[0.011156] Initializing cgroup subsys perf_event

Is cgroup memory really disabled ?

Anyway, I still have the same messages :

May  7 20:06:48 crapaud64 console-kit-daemon[2468]: WARNING: Failed to
add monitor on '/dev/pts/2': No space left on device
May  7 20:07:04 crapaud64 console-kit-daemon[2468]: WARNING: Failed to
add monitor on '/dev/tty1': No space left on device

Sebastien


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/can64bfaef51+exv4ye+bv_bey5pts0pu3aqg505gm6nthbq...@mail.gmail.com

Re: Weird warning from console-kit-daemon

2012-05-06 Thread Camaleón 
On Sun, 06 May 2012 19:29:45 +0200, Sébastien Kalt wrote:

Sébastien, please, avoid using html formatted messages.

> 2012/5/6 Camaleón 

>> Hi... I almost had forgotten this thread.
>>
> Sorry, but I have a 50 Go virtual machine that I need for work, so I had
> to wait for some time off.

It's okay, it's just that I had to re-read the whole thread again :-)

>>  Okay, we can safely discard a space issue.
>>
>> Let's see what Google suggests... look:
>>
>> http://ubuntuforums.org/showthread.php?t=1777400
>>
>> You can try that. If it makes any difference then we'll have
>> investigate what can be the drawbacks of disabling memory cgroups :-)
^

Errata, that must be "enabling".

> I had seen that, but neither my /boot/grub/grub.conf nor my
> /etc/default/grub have any "cgroup_disable=memory", but I might not
> search in the right place, I've been confused with grub since version 2
> :/

Mmm, then you can try with the opposite, i.e., adding it. 

When you get the GRUB menu, select the line you want to boot and press 
"e" to get into the edit mode. From there, place the cursor in the kernel 
line and append at the end "cgroup_disable=memory" without quotes. Then 
press F10 to normally boot your system.

> Is it possible, after boot, to see which options where given to grub ?

You mean the kernel options, right? Yes, from many places, but the 
quicker can be "dmesg":

sm01@stt008:~$ dmesg | grep -i "kernel command"
[0.00] Kernel command line: root=/dev/sda3 ro vga=0x31A

Form there we get the options passed to the kernel: "ro vga=0x31A".

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jo6dc1$kir$1...@dough.gmane.org

Re: Weird warning from console-kit-daemon

2012-05-06 Thread Sébastien Kalt 
2012/5/6 Sébastien Kalt 

>
> Is it possible, after boot, to see which options where given to grub ?
>
Hum, sorry, in the first lines of dmesg :

Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=d30adeed-998c-4f8b-b25c-185113da1cda ro quiet

Sebastien

Re: Weird warning from console-kit-daemon

2012-05-06 Thread Sébastien Kalt 
2012/5/6 Camaleón 

On Sun, 06 May 2012 16:14:53 +0200, Sébastien Kalt wrote:
>
> > Hi Camaleón,
>
> Hi... I almost had forgotten this thread.
>
Sorry, but I have a 50 Go virtual machine that I need for work, so I had to
wait for some time off.


>  Okay, we can safely discard a space issue.
>
> Let's see what Google suggests... look:
>
> http://ubuntuforums.org/showthread.php?t=1777400
>
> You can try that. If it makes any difference then we'll have investigate
> what can be the drawbacks of disabling memory cgroups :-)
>
I had seen that, but neither my /boot/grub/grub.conf nor my
/etc/default/grub have any "cgroup_disable=memory", but I might not search
in the right place, I've been confused with grub since version 2 :/

Is it possible, after boot, to see which options where given to grub ?

Sebastien

Re: Weird warning from console-kit-daemon

2012-05-06 Thread Camaleón 
On Sun, 06 May 2012 16:14:53 +0200, Sébastien Kalt wrote:

> Hi Camaleón,

Hi... I almost had forgotten this thread.
 
> Thank you for your answer, but I still think physical hard drive space
> is not the problem.
> 
> Anyway, as you asked, I freed some space :
> 
> $ df -h
> Filesystem  Size  Used Avail Use% 
> Mounted on
> rootfs  153G  101G   45G 70% /
> udev1.9G 0  1.9G 0% 
> /dev
> tmpfs   390M  408K  390M 1% 
> /run
> /dev/disk/by-uuid/d30adeed-998c-4f8b-b25c-185113da1cda  153G  101G   45G 70% /
> tmpfs   5.0M 0  5.0M 0% 
> /run/lock
> tmpfs   780M  240K  779M 1% 
> /tmp
> tmpfs   780M   76K  780M 1% 
> /run/shm

Much better.

> And I still have the messages :
> 
> May  6 13:57:10 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add 
> monitor on '/dev/tty1': No space left on device 
> May  6 13:57:11 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add 
> monitor on '/dev/pts/1': No space left on device 
> May  6 13:57:40 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add 
> monitor on '/dev/tty1': No space left on device 
> May  6 13:57:41 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add 
> monitor on '/dev/pts/1': No space left on device
> 
> I'll continue to search the web for those messages, and if I find an
> answer or an explanation elsewhere, I'll forward it to this list.

Okay, we can safely discard a space issue.

Let's see what Google suggests... look:

http://ubuntuforums.org/showthread.php?t=1777400

You can try that. If it makes any difference then we'll have investigate 
what can be the drawbacks of disabling memory cgroups :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jo62d9$kir$1...@dough.gmane.org

Re: Weird warning from console-kit-daemon

2012-05-06 Thread Sébastien Kalt 
Hi Camaleón,

Thank you for your answer, but I still think physical hard drive space is
not the problem.

Anyway, as you asked, I freed some space :

$ df -h
Filesystem  Size  Used Avail
Use% Mounted on
rootfs  153G  101G   45G
70% /
udev1.9G 0  1.9G
0% /dev
tmpfs   390M  408K  390M
1% /run
/dev/disk/by-uuid/d30adeed-998c-4f8b-b25c-185113da1cda  153G  101G   45G
70% /
tmpfs   5.0M 0  5.0M
0% /run/lock
tmpfs   780M  240K  779M
1% /tmp
tmpfs   780M   76K  780M
1% /run/shm

And I still have the messages :

May  6 13:57:10 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add
monitor on '/dev/tty1': No space left on device
May  6 13:57:11 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add
monitor on '/dev/pts/1': No space left on device
May  6 13:57:40 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add
monitor on '/dev/tty1': No space left on device
May  6 13:57:41 crapaud64 console-kit-daemon[2564]: WARNING: Failed to add
monitor on '/dev/pts/1': No space left on device

I'll continue to search the web for those messages, and if I find an answer
or an explanation elsewhere, I'll forward it to this list.

Greetings,

Sebastien

Re: Weird warning from console-kit-daemon

2012-04-19 Thread Camaleón 
On Thu, 19 Apr 2012 08:40:39 +0200, Sébastien Kalt wrote:

> I'm using Debian Sid on my laptop.
> 
> I'm having tons of warnings from console-kit-daemon in /var/log/syslog :
> 
> Apr 19 08:18:35 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
> add monitor on '/dev/pts/1': No space left on device 

(...)

> My hard drive is not full :

Are you sure?

> $ df -h
> Filesystem  Size  Used Avail Use% 
> Mounted on
> rootfs  153G  142G  3.5G  98% 
> / 
> udev1.9G 0 1.9G   0%  
> /dev
> tmpfs   390M  456K 390M   1%  
> /run
> /dev/disk/by-uuid/d30adeed-998c-4f8b-b25c-185113da1cda  153G  142G  3.5G  98% 
> / 
> tmpfs   5.0M 0 5.0M   0%  
> /run/lock
> tmpfs   780M  248K 779M   1%  
> /tmp
> tmpfs   780M   80K 780M   1%  
> /run/shm

Mmm... but your "/" partition is almost full (~4 GiB of free space is not 
that much). Try to clean your apt cache data (apt-get clean) to make room, 
just in case.
 
Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jmpg8m$kai$1...@dough.gmane.org

Weird warning from console-kit-daemon

2012-04-18 Thread Sébastien Kalt 
Hello,

I'm using Debian Sid on my laptop.

I'm having tons of warnings from console-kit-daemon in /var/log/syslog :

Apr 19 08:18:35 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:18:51 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device
Apr 19 08:19:05 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:19:21 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device
Apr 19 08:19:35 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:19:51 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device
Apr 19 08:20:05 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:20:21 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device
Apr 19 08:20:35 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:20:51 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device

My hard drive is not full :

$ df -h
Filesystem  Size  Used
Avail Use% Mounted on
rootfs  153G  142G  3.5G  98% /
udev1.9G 0
1.9G   0% /dev
tmpfs   390M  456K
390M   1% /run
/dev/disk/by-uuid/d30adeed-998c-4f8b-b25c-185113da1cda  153G  142G  3.5G  98% /
tmpfs   5.0M 0
5.0M   0% /run/lock
tmpfs   780M  248K
779M   1% /tmp
tmpfs   780M   80K
780M   1% /run/shm

I have those warnings when I launch my session under user1, and then I
su - user2 in a urxvt console (pts/0 this morning) and/or I launch an
application under user2 with gksu -u user2 iceweasel (pts/2 this
morning).

If I login under user2 in a console, like tty2, then I have the same
kind of messages :

Apr 19 08:34:21 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/0': No space left on device
Apr 19 08:34:35 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/pts/1': No space left on device
Apr 19 08:34:36 crapaud64 console-kit-daemon[2041]: WARNING: Failed to
add monitor on '/dev/tty2': No space left on device

I can work without any troubles on my laptop, so it might not be very
serious, nor a bug.

But I like to know why warnings are issued, and I didn't find anything
on the web (but I'm quite bad at searching with keywords).

Has anybody an idea ?

Sebastien


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAN64BFYRtDe8BKpbVYHLR7JeAdZKse-JY8a3kXhD=n9pque...@mail.gmail.com