On Fri, 20 Jul 2012 18:19:45 +0100, Brian wrote:
> On Fri 20 Jul 2012 at 17:07:41 +, Camaleón wrote:
>> > If only for its debugging technique you might want to look at
>> >
>> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548863
>> >
>> > Also, you could use chmod 644 on gnome-pty-h
On Fri 20 Jul 2012 at 17:07:41 +, Camaleón wrote:
> On Fri, 20 Jul 2012 17:33:26 +0100, Brian wrote:
>
> > On Fri 20 Jul 2012 at 14:26:38 +, Camaleón wrote:
>
> >> Well, I have found a cron task that runs this thingy every 10 minutes
> >> (?), I wonder if that's the expected but for sure
On Fri, 20 Jul 2012 17:33:26 +0100, Brian wrote:
> On Fri 20 Jul 2012 at 14:26:38 +, Camaleón wrote:
>> Well, I have found a cron task that runs this thingy every 10 minutes
>> (?), I wonder if that's the expected but for sure it was not me who put
>> that task in place :-?
>
> If only for i
On Fri 20 Jul 2012 at 14:26:38 +, Camaleón wrote:
> On Thu, 19 Jul 2012 19:45:37 +0100, Brian wrote:
>
> > What you are being shown is a list of processes which are still being
> > run. It does not imply sendsigs was unable to kill all of them. If you
> > look at the screen output you will se
On Thu, 19 Jul 2012 19:45:37 +0100, Brian wrote:
> On Thu 19 Jul 2012 at 18:01:54 +, Camaleón wrote:
>
>> On Thu, 19 Jul 2012 18:19:10 +0100, Brian wrote:
>>
>> You mean that a single (unknown) process avoids the rest from stopping?
>
> No.
>
>> That would be even worst... Or maybe is that
On Thu 19 Jul 2012 at 18:01:54 +, Camaleón wrote:
> On Thu, 19 Jul 2012 18:19:10 +0100, Brian wrote:
>
> You mean that a single (unknown) process avoids the rest from stopping?
No.
> That would be even worst... Or maybe is that the printed FAILED message
> is misleading? :-?
Not this, eit
On Thu, 19 Jul 2012 18:19:10 +0100, Brian wrote:
> On Thu 19 Jul 2012 at 14:55:56 +, Camaleón wrote:
>
>> On Thu, 19 Jul 2012 10:26:21 +0100, Brian wrote:
>>
>> > I think neither rsyslogd nor rpcbind is the problem here.
>>
>> Well, they seem to fail to be stopped when I shutdown or restart
On Thu 19 Jul 2012 at 14:55:56 +, Camaleón wrote:
> On Thu, 19 Jul 2012 10:26:21 +0100, Brian wrote:
>
> > I think neither rsyslogd nor rpcbind is the problem here.
>
> Well, they seem to fail to be stopped when I shutdown or restart the
> system :-?
They are casualties, not causes. rsyslo
On Thu, 19 Jul 2012 10:26:21 +0100, Brian wrote:
> On Wed 18 Jul 2012 at 14:25:49 +, Camaleón wrote:
>
>> Any idea on how could I debug this?
>>
>> I'm considering in opening a bug report because messages are still
>> there for rsyslogd and gnome-helper-pty (I have disabled "rpcbind"
>> serv
On Wed 18 Jul 2012 at 14:25:49 +, Camaleón wrote:
> On Thu, 12 Jul 2012 16:03:58 +, Camaleón wrote:
>
> > I'm running an updated wheezy and since weeks ago, when shutting down
> > (or restarting) the system I can see this message:
> >
> > [FAIL] Killing all remaining processes... failed.
On Thu, 12 Jul 2012 16:03:58 +, Camaleón wrote:
> I'm running an updated wheezy and since weeks ago, when shutting down
> (or restarting) the system I can see this message:
>
> [FAIL] Killing all remaining processes... failed.
(...)
> Anyone seeing this message? If not, how could I debug wh
On Sat, 14 Jul 2012 11:30:18 +0200, Claudius Hubig wrote:
> Hello Camaleón,
>
> Camaleón wrote:
>> init-+-exe
>> |-rc---startpar---sendsigs---pstree
>> |-rpcbind
>
> Could you, on a running system, check whether an ‘exe’ process is
> running and to whom it belongs? rpcbind belongs to
On Sat, 14 Jul 2012 10:23:52 +0100, Brian wrote:
> On Fri 13 Jul 2012 at 17:27:11 +, Camaleón wrote:
>
>> Mmm, there's still a FAILED message BUT now rsyslog is not listed, just
>> the other two proccesses:
>>
>> init-+-exe
>> |-rc---startpar---sendsigs---pstree
>> |-rpcbind
>>
>>
Hello Camaleón,
Camaleón wrote:
> init-+-exe
> |-rc---startpar---sendsigs---pstree
> |-rpcbind
Could you, on a running system, check whether an ‘exe’ process is
running and to whom it belongs? rpcbind belongs to NFS, IIRC (also a
possible service to disable), and the other line is pstr
On Fri 13 Jul 2012 at 17:27:11 +, Camaleón wrote:
> Mmm, there's still a FAILED message BUT now rsyslog is not listed, just
> the other two proccesses:
>
> init-+-exe
> |-rc---startpar---sendsigs---pstree
> |-rpcbind
>
> So, now I have to find why these are failing to be properly
On Thu, 12 Jul 2012 18:32:50 +0100, Brian wrote:
> On Thu 12 Jul 2012 at 16:03:58 +, Camaleón wrote:
>
>> I'm running an updated wheezy and since weeks ago, when shutting down
>> (or restarting) the system I can see this message:
>>
>> [FAIL] Killing all remaining processes... failed.
(...)
On Thu 12 Jul 2012 at 16:03:58 +, Camaleón wrote:
> I'm running an updated wheezy and since weeks ago, when shutting down (or
> restarting) the system I can see this message:
>
> [FAIL] Killing all remaining processes... failed.
>
> (here is a snapshot)
>
> http://picpaste.com/shutdown_err
On Thu, 12 Jul 2012 11:32:11 -0500, hvw59601 wrote:
> Camaleón wrote:
>> I'm running an updated wheezy and since weeks ago, when shutting down
>> (or restarting) the system I can see this message:
>>
>> [FAIL] Killing all remaining processes... failed.
>>
>
> Running wheezy also, but I haven'
Camaleón wrote:
Hello,
I'm running an updated wheezy and since weeks ago, when shutting down (or
restarting) the system I can see this message:
[FAIL] Killing all remaining processes... failed.
Running wheezy also, but I haven't done a dist-upgrade since June 19th.
I get an [ok] for tha
Hello,
I'm running an updated wheezy and since weeks ago, when shutting down (or
restarting) the system I can see this message:
[FAIL] Killing all remaining processes... failed.
(here is a snapshot)
http://picpaste.com/shutdown_error-rEoKsztL.png
There are no more errors (I mean, system is ru
20 matches
Mail list logo
