David Wright writes:
> On Mon 20 Feb 2023 at 10:39:21 (+0100), Andreas Leha wrote:
>> Greg Wooledge writes:
>> > On Sun, Feb 19, 2023 at 12:04:22PM -0600, David Wright wrote:
>> >> But even that's not enough
>> >> because the field widt
Hi all,
Unfortunately I can't trace exactly how I got myself in this situation,
but right now, xdm does not autostart for me.
Largely, what I did: Install bullseye without GUI but install xdm later
manually. I also upgraded to bookworm (for other reasons). It might
well be that the issue is not
Greg Wooledge writes:
> On Sun, Feb 19, 2023 at 12:04:22PM -0600, David Wright wrote:
>> But even that's not enough
>> because the field width is somewhat variable: try ps -eo '%c | %z | %a'
>> (We can still use | to make the problem somewhat more obvious.)
>
> Oh wow. Yeah, OK, that's not
Reco writes:
> Hi.
>
> On Fri, Feb 17, 2023 at 07:46:23AM +0100, Andreas Leha wrote:
>> Now my question: How can I restore the previous behaviour that allowed
>> other than whitespace separators between fields?
>
> diff -purw procps-3.3.17/ps/sortformat.c procp
Hi all,
I am facing a strange issue. This command used to work
ps -eo '%p|%C'
Now, on a debian testing machine only
ps -eo '%p %C'
works. Running
ps -eo '%p|%C'
results in this error:
error: improper AIX field descriptor
ps --version says 'ps from procps-ng 4.0.2'
Now my questio
Roberto C. Sánchez writes:
> On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>>
>> Dear Tomas,
>>
>> Thanks for the swift reply!
>>
>> OK, then I should do `quilt pop -a` before the second compilation,
>> right?
>>
>> But
writes:
> On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
>> Dear all,
>>
>> I am re-compiling xscreensaver.
>>
>> Re-compiling once works fine:
>>
>> apt-get source xscreensaver
>> cd xscreensaver-6.0.6+dfsg1
>
Dear all,
I am re-compiling xscreensaver.
Re-compiling once works fine:
apt-get source xscreensaver
cd xscreensaver-6.0.6+dfsg1
LANG=C debuild -us -uc
Re-compiling a second time errors out, though:
> LANG=C debuild -us -uc
(skipped lines)
dpkg-source: info: using
Hi all,
thanks for all your suggestions and help. I chose to re-install now, as
I am not able to spend more time on this issue.
Although I would have loved to know what caused the error in the end,
the re-install fixed it and was cheaper than a continued search for the
cause.
Thanks again for a
Hi Vincent,
thanks again for all your help.
Vincent Lefevre writes:
> On 2013-04-24 23:38:06 +0200, Andreas Leha wrote:
>> Vincent Lefevre writes:
>> > On 2013-04-24 05:03:53 +0200, Andreas Leha wrote:
>> >> Vincent Lefevre writes:
>> >> >> BT
Andreas Leha writes:
> Hi Jean-Marc,
>
> thanks for your suggestions. See the results inline.
>
> Jean-Marc writes:
>
>> On Wed, 24 Apr 2013 05:03:53 +0200, Andreas Leha
>> wrote:
>> Hi Andreas,
>>
>> Did you check your sshd config' ?
&
Hi Vincent,
thanks for staying on this!
Vincent Lefevre writes:
> On 2013-04-24 05:03:53 +0200, Andreas Leha wrote:
>> Vincent Lefevre writes:
>> >> BTW, does "ssh -t localhost" work on both machines?
>>
>> I am not sure. On the &#
Hi Jean-Marc,
thanks for your suggestions. See the results inline.
Jean-Marc writes:
> On Wed, 24 Apr 2013 05:03:53 +0200, Andreas Leha
> wrote:
> Hi Andreas,
>
> Did you check your sshd config' ?
> You can do it running:
> sshd -t
I get nothing -- which I
Hi Vincent,
Vincent Lefevre writes:
> On 2013-04-24 00:24:16 +0200, Vincent Lefevre wrote:
>> On 2013-04-23 23:05:27 +0200, Andreas Leha wrote:
>> > Here is what I get:
>> > ,
>> > | > ssh -t root@192.168.2.109 bash
>> > | Connection to 192.
Vincent Lefevre writes:
> On 2013-04-22 22:49:23 +0200, Andreas Leha wrote:
>> thanks for that. Here is what I get:
>> ,
>> | + '[' -z '' ']'
>> | + return
>> | Connection to 192.168.2.109 closed.
>> `
>
> You
Guido Martínez writes:
> Hi,
>
> On Mon, Apr 22, 2013 at 5:49 PM, Andreas Leha
> wrote:
>> thanks for that. Here is what I get:
>> ,
>> | + '[' -z '' ']'
>> | + return
>> | Connection to 192.168.2.109 closed.
>>
Hi Bob, Guido, and Vincent
Vincent Lefevre writes:
> On 2013-04-22 22:49:23 +0200, Andreas Leha wrote:
>> thanks for that. Here is what I get:
>> ,
>> | + '[' -z '' ']'
>> | + return
>> | Connection to 192.168.2.109 closed.
Hi Bob,
Bob Proulx writes:
> Andreas Leha wrote:
>> I have the problem that my ssh session terminates immediately after
>> logging in.
>
> I don't see a problem with the files you included. But I would still
> suspect a problem in there.
>
> To debug this
Hi Jochen,
thanks for taking this up.
Jochen Spieker writes:
> Andreas Leha:
>>
>> Short Version:
>> I have the problem that my ssh session terminates immediately after
>> logging in.
>
> What's the users' shell on the server? It is the last column
Hi all,
Short Version:
I have the problem that my ssh session terminates immediately after
logging in.
Longer Version:
I am running debian squeeze on a client and on a 'server'. The server
is actually a pogoplug on which I installed debian squeeze following
http://projects.doozan.com/debian/.
writes:
> Andreas Leha wrote:
>> No one?
>> Is there anything, I should add to the question?
>
> Since no one else is jumping in...
>> Consider this stripped down script (placed at
>> /usr/local/bin/testinotify) around inotifywait:
>>
>> #+begin_src sh
&
Andreas Leha writes:
> Hi all,
>
>
> (cross-post from here:
> http://superuser.com/questions/571416/start-stop-daemon-on-an-inotify-scripti)
>
>
>
> I am on debian squeeze.
>
> Consider this stripped down script (placed at
> /usr/local/bin/testinotify) ar
Hi all,
(cross-post from here:
http://superuser.com/questions/571416/start-stop-daemon-on-an-inotify-scripti)
I am on debian squeeze.
Consider this stripped down script (placed at
/usr/local/bin/testinotify) around inotifywait:
#+begin_src sh
#!/bin/bash
WATCHDIR="/tmp/testinotify"
23 matches
Mail list logo
