Re: tmux fails to redraw on \n
solved with tty.c r1.51
thanks,
C.
On Sat, Oct 17, 2009 at 05:47:00PM +0100, Nicholas Marriott wrote:
> Hi
>
> Can you make sure you are running HEAD as of this morning (tty.c r1.51) and
> see
> if this still happens?
>
> If it does, please try C-b r after the problem happens and tell me if it
> redraws the screen correctly then.
>
> Also please do the following (this procedure also works for anyone else who
> would like to report redraw bugs):
>
> 1. Create a file suitable to demonstrate the problem
>
> 2. Do:
>
> pkill tmux
> tmux - new
>
> 3. Reproduce the problem with the minimum of commands/cursor movement.
>
> 4. *While the problem is still on screen*, ie don't cause tmux redraw or do
>anything else, go to a terminal *outside* tmux and do pkill -9 tmux.
>
> 5. Send me the tmux-*.log and tmux.out files which should have been created in
>the dir where you started tmux.
>
> It is fine for the client log to be empty. If you have no server log file, you
> didn't kill all running tmux processes before running with -.
>
> Also please send me your .tmux.conf if you have one.
>
> Thanks
>
>
> On Sat, Oct 17, 2009 at 05:29:03PM +0100, gar wrote:
> > Hi guys,
> > I noted this behaviour on tmux using vim:
> >
> >int
> >main() {
> >return;
> >}
> >
> > If I go to 2nd line and press enter, I have:
> >
> > int
> > main() {
> > main() {
> > return;
> > }
> >
> > This _not_ happens if there's no characters on first
> > column.
> >
> >int
> >main() {
> > return;
> >}
> >
> > If I go to 3d line and press enter, nothing happens.
> >
> > This beahviour _is_ related _only_ to screen drawing,
> > in fact the file is not changed (there're no lines
> > added)
> >
> > I noted this from snapshots > 1 october, I've tested it
> > with tmux on a snapshot < 25 september and it's ok.
> >
> > Ah, I've a _simple_ .vimrc, just a copy of (+/-)
> > vimrc_example...
> >
> > Comments?
> >
> > C.
Re: type of softraid
ok, so what does 0x4c means? regards, c. On 13/12/08 08:52 -0600, Marco Peereboom wrote: > Crypto > > On Sat, Dec 13, 2008 at 03:42:27PM +0100, Cesare Gargano wrote: > > On 12/12/08 11:07 -0600, Marco Peereboom wrote: > > > It isn't pretty but: > > > dd if=/dev/wd1a skip=8244 bs=1 count=4 | hexdump -C > > > 4+0 records in > > > 4+0 records out > > > 4 bytes transferred in 0.001 secs (3263 bytes/sec) > > > 41 00 00 00 |A...| > > > 0004 > > > > > > wd1a is the cooked RAID partition. In this case this is an AOE target. > > > If it was crypto it would have been 4c 00 00 00 |C...| > > > > > > Currently the possible values are: 0x00 (RAID 0), 0x01 (RAID 1), 0x41 > > > (AOE target), 0x4c (CRYPTO) & 0x61 (AOE initiator). > > > Note that softraid is not endian neutral so on big endian machines the > > > numbers are flipped. > > > > > > wd0i is my RAID partition: > > > > .. $ dd if=/dev/wd0i skip=8244 bs=1 count=4 | hexdump -C > > 4+0 records in > > 4+0 records out > > 4 bytes transferred in 0.000 secs (11799 bytes/sec) > > 43 00 00 00 |C...| > > 0004 > > .. $ > > > > what does 0x43 means? > > > > regards, > > c. > > > > > > > > FWIW, > > > /marco > > > > > > On Fri, Dec 12, 2008 at 01:33:14PM +0100, Michael wrote: > > > > Todd T. Fries schrieb: > > > > > tried > > > > > > > > > > bioctl -h softraid0 > > > > > lately? > > > > > > > > > > > > Well, yes... but it only works if I already activated the softraid > > > > device... > > > > > > > > # bioctl -h softraid0 > > > > Volume Status Size Device > > > > softraid0 0 Online 3.8G sd1 CRYPTO > > > > 0 Online 3.8G 0:0.0 noencl > > > > # bioctl -d sd1 > > > > # bioctl -h softraid0 > > > > > > > > > > > > ...but I would like to know what kind of type sd0a is before I try to > > > > use > > > > > > > > bioctl -c [01C] -l /dev/... softraid0 > > > > > > > > to be able to use bioctl from a script, only for CRYPTO. > > > > > > > > Only other way I currently see is to set the label from disklabel of sd0 > > > > to some name and check what to do from that information.
Re: type of softraid
On 12/12/08 11:07 -0600, Marco Peereboom wrote: > It isn't pretty but: > dd if=/dev/wd1a skip=8244 bs=1 count=4 | hexdump -C > 4+0 records in > 4+0 records out > 4 bytes transferred in 0.001 secs (3263 bytes/sec) > 41 00 00 00 |A...| > 0004 > > wd1a is the cooked RAID partition. In this case this is an AOE target. > If it was crypto it would have been 4c 00 00 00 |C...| > > Currently the possible values are: 0x00 (RAID 0), 0x01 (RAID 1), 0x41 > (AOE target), 0x4c (CRYPTO) & 0x61 (AOE initiator). > Note that softraid is not endian neutral so on big endian machines the > numbers are flipped. wd0i is my RAID partition: .. $ dd if=/dev/wd0i skip=8244 bs=1 count=4 | hexdump -C 4+0 records in 4+0 records out 4 bytes transferred in 0.000 secs (11799 bytes/sec) 43 00 00 00 |C...| 0004 .. $ what does 0x43 means? regards, c. > > FWIW, > /marco > > On Fri, Dec 12, 2008 at 01:33:14PM +0100, Michael wrote: > > Todd T. Fries schrieb: > > > tried > > > > > > bioctl -h softraid0 > > > lately? > > > > > > Well, yes... but it only works if I already activated the softraid device... > > > > # bioctl -h softraid0 > > Volume Status Size Device > > softraid0 0 Online 3.8G sd1 CRYPTO > > 0 Online 3.8G 0:0.0 noencl > > # bioctl -d sd1 > > # bioctl -h softraid0 > > > > > > ...but I would like to know what kind of type sd0a is before I try to use > > > > bioctl -c [01C] -l /dev/... softraid0 > > > > to be able to use bioctl from a script, only for CRYPTO. > > > > Only other way I currently see is to set the label from disklabel of sd0 > > to some name and check what to do from that information.
startx strange behaviour
Hi all! If I start X with startx command and then open a xterm and run 'ps a', I get: .. 13237 ?? R 0:04.69 /usr/X11R6/bin/X :0 -auth /home/gar/.serverauth.6053 (Xorg) 18053 ?? I 0:00.01 X: [priv] (Xorg) 9547 p1 Ss 0:00.02 -ksh (ksh) 1024 p1 R+ 0:00.00 ps -xa 26534 C0 Is 0:00.06 -ksh (ksh) 6053 C0 I+ 0:00.01 /bin/sh ./bin/startx 21582 C0 I+ 0:00.01 xinit /home/gar/.xinitrc -- /usr/X11R6/bin/X -auth /home/gar/.serverauth.6053 26851 C0 I 0:00.00 sh /home/gar/.xinitrc .. mh, ok. If I start X with startx command and _server options_, like this: $ startx -- -br -nolisten tcp -once and then open a xterm and run 'ps a', I get: .. 13237 ?? R 0:04.69 /usr/X11R6/bin/X :0 -auth /home/gar/.serverauth.6054 (Xorg) 18053 ?? I 0:00.01 X: [priv] (Xorg) 9547 p1 Ss 0:00.02 -ksh (ksh) 1024 p1 R+ 0:00.00 ps -xa 26534 C0 Is 0:00.06 -ksh (ksh) 27672 C0 I+ 0:00.01 /bin/sh /usr/X11R6/bin/startx /usr/X11R6/bin/startx /usr/X11R6/bin/startx /usr/X11R6/bin/startx ... 12927 C0 I+ 0:00.01 xinit /home/gar/.xinitrc -- /usr/X11R6/bin/X -br -nolisten tcp -once -auth /home/gar/.serverauth.27672 17622 C0 I 0:00.00 sh /home/gar/.xinitrc .. Now, is this line a bit strange? 27672 C0 I+ 0:00.01 /bin/sh /usr/X11R6/bin/startx /usr/X11R6/bin/startx /usr/X11R6/bin/startx /usr/X11R6/bin/startx ... For each server argument passed to startx _after_ '--', there is a /usr/.../startx, caused by (in /usr/X11R6/bin/startx): .. whoseargs="client" while [ x"$1" != x ]; do case "$1" in # '' required to prevent cpp from treating "/*" as a C comment. /''*|\./''*) if [ "$whoseargs" = "client" ]; then if [ x"$clientargs" = x ]; then client="$1" else clientargs="$clientargs $1" fi else if [ x"$serverargs" = x ]; then server="$1" else serverargs="$serverargs $1" fi fi ;; --) whoseargs="server" ;; *) if [ "$whoseargs" = "client" ]; then clientargs="$clientargs $1" else # display must be the FIRST server argument if [ x"$serverargs" = x ] && \ expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then display="$1" else serverargs="$serverargs $1" fi fi ;; esac shift done . comments? C.
Re: Google in "shell" - looks interesting
On 04/06/08 07:59 -0700, Marti Martinez wrote: > Meh. Doesn't work with lynx. Why bother? > > On Wed, Jun 4, 2008 at 6:17 AM, Cesare Gargano > <[EMAIL PROTECTED]> wrote: > > On 04/06/08 13:39 +0100, Tomas Bodzar wrote: > >> http://goosh.org > >> > >> > > > > Great. > > > > > > > > -- > Systems Programmer, Principal > Electrical & Computer Engineering > The University of Arizona > [EMAIL PROTECTED] > > ?
Re: Google in "shell" - looks interesting
On 04/06/08 13:39 +0100, Tomas Bodzar wrote: > http://goosh.org > > Great.
Re: Small diff to make dhclient(8) go to background immediately
On 19/05/08 15:50 +0200, Cesare Gargano wrote:
> On 18/05/08 17:20 +0200, Jona Joachim wrote:
> > I very much appreciate the work of reyk@ on dhclient to make it renew the
> > lease when the
> > link is lost. However it might happen that you don't have a link at the
> > moment where
> > you launch dhclient but you know that you might get a link afterwards.
> > This is true when you launch your laptop somewhere where you have wifi
> > connectivity
> > but unfortunately you're in a spot where you don't currently receive it.
> > If you specify 'dhcp' in hostname. you will have to wait until dhclient
> > times out
> > or hit Ctrl-C at startup.
> > This tiny patch adds an option to dhclient to tell it to just go into
> > background and wait
> > until you get a link.
> >
> > I would appreciate any comments.
> > Thanks!
> >
> >
> > Index: dhclient.c
> > ===
> > RCS file: /cvs/src/sbin/dhclient/dhclient.c,v
> > retrieving revision 1.118
> > diff -u -r1.118 dhclient.c
> > --- dhclient.c 9 May 2008 05:19:14 - 1.118
> > +++ dhclient.c 18 May 2008 15:11:53 -
> > @@ -253,7 +253,7 @@
> > int
> > main(int argc, char *argv[])
> > {
> > - int ch, fd, quiet = 0, i = 0, pipe_fd[2];
> > + int ch, fd, quiet = 0, background = 0, i = 0, pipe_fd[2];
> > extern char *__progname;
> > struct passwd *pw;
> >
> > @@ -261,8 +261,11 @@
> > openlog(__progname, LOG_PID | LOG_NDELAY, DHCPD_LOG_FACILITY);
> > setlogmask(LOG_UPTO(LOG_INFO));
> >
> > - while ((ch = getopt(argc, argv, "c:dl:qu")) != -1)
> > + while ((ch = getopt(argc, argv, "bc:dl:qu")) != -1)
> > switch (ch) {
> > + case 'b':
> > + background = 1;
> > + break;
> > case 'c':
> > path_dhclient_conf = optarg;
> > break;
> > @@ -319,6 +322,9 @@
> >
> > read_client_conf();
> >
> > + if (background)
> > + goto dispatch;
> > +
> > if (!(ifi->linkstat = interface_link_status(ifi->name))) {
> > fprintf(stderr, "%s: no link ...", ifi->name);
> > if (config->link_timeout == 0) {
> > @@ -409,7 +415,7 @@
> > {
> > extern char *__progname;
> >
> > - fprintf(stderr, "usage: %s [-dqu] [-c file] [-l file] interface\n",
> > + fprintf(stderr, "usage: %s [-bdqu] [-c file] [-l file] interface\n",
> > __progname);
> > exit(1);
> > }
> >
> >
>
> Ehi! Your diff is already there!
>
> cat /etc/dhclient.conf
> link_timeout 0;
is link-timeout
Ehm! Enjoy!
>
> It works!
Re: Small diff to make dhclient(8) go to background immediately
On 18/05/08 17:20 +0200, Jona Joachim wrote:
> I very much appreciate the work of reyk@ on dhclient to make it renew the
> lease when the
> link is lost. However it might happen that you don't have a link at the
> moment where
> you launch dhclient but you know that you might get a link afterwards.
> This is true when you launch your laptop somewhere where you have wifi
> connectivity
> but unfortunately you're in a spot where you don't currently receive it.
> If you specify 'dhcp' in hostname. you will have to wait until dhclient
> times out
> or hit Ctrl-C at startup.
> This tiny patch adds an option to dhclient to tell it to just go into
> background and wait
> until you get a link.
>
> I would appreciate any comments.
> Thanks!
>
>
> Index: dhclient.c
> ===
> RCS file: /cvs/src/sbin/dhclient/dhclient.c,v
> retrieving revision 1.118
> diff -u -r1.118 dhclient.c
> --- dhclient.c 9 May 2008 05:19:14 - 1.118
> +++ dhclient.c 18 May 2008 15:11:53 -
> @@ -253,7 +253,7 @@
> int
> main(int argc, char *argv[])
> {
> - int ch, fd, quiet = 0, i = 0, pipe_fd[2];
> + int ch, fd, quiet = 0, background = 0, i = 0, pipe_fd[2];
> extern char *__progname;
> struct passwd *pw;
>
> @@ -261,8 +261,11 @@
> openlog(__progname, LOG_PID | LOG_NDELAY, DHCPD_LOG_FACILITY);
> setlogmask(LOG_UPTO(LOG_INFO));
>
> - while ((ch = getopt(argc, argv, "c:dl:qu")) != -1)
> + while ((ch = getopt(argc, argv, "bc:dl:qu")) != -1)
> switch (ch) {
> + case 'b':
> + background = 1;
> + break;
> case 'c':
> path_dhclient_conf = optarg;
> break;
> @@ -319,6 +322,9 @@
>
> read_client_conf();
>
> + if (background)
> + goto dispatch;
> +
> if (!(ifi->linkstat = interface_link_status(ifi->name))) {
> fprintf(stderr, "%s: no link ...", ifi->name);
> if (config->link_timeout == 0) {
> @@ -409,7 +415,7 @@
> {
> extern char *__progname;
>
> - fprintf(stderr, "usage: %s [-dqu] [-c file] [-l file] interface\n",
> + fprintf(stderr, "usage: %s [-bdqu] [-c file] [-l file] interface\n",
> __progname);
> exit(1);
> }
>
>
Ehi! Your diff is already there!
cat /etc/dhclient.conf
link_timeout 0;
It works!
Re: ACPI issue
On 11/05/08 16:39 +0200, Cesare Gargano wrote:
> Hi all.
> I'm playing with acpi to get it working on my T23 thinkpad.
> Thermal zone and battery status are working ok. But when I play with hotkey
> buttons, open/close lid, unplug AC cable, nothing happens. After reading
> acpi.c
> I've noted that this line is not correct for me (from [EMAIL PROTECTED]):
>
> ...
> sc->sc_lastgpe = sc->sc_fadt->gpe0_blk_len << 2;
> ...
>
> because I've a GPE on 0x18 and another on 0x1c, but sc_lastgpe value is 0x10.
> Reading my acpidump output, I find:
>
> ...
> Device(EC__) {
> Name(_HID, 0x090cd041)
> Name(_UID, 0x0)
> Name(_GPE, 0x1c)
>
> ...
> ...
> Scope(\_GPE) {
> Method(_L18) {
> ^^
> Store(\_SB_.PCI0.LPC_.EC__.HWAK, Local0)
> ...
>
> If I change that line to:
>
> ...
> sc->sc_lastgpe = ((sc->sc_fadt->gpe0_blk_len << 2) * 8) - 1;
> ...
>
> (from acpica-unix version, found on netbsd source code), I don't know what I'm
> doing, but it works. I can see these lines in dmesg:
>
> ...
> Adding GPE handler 18 (level)
> ...
> Adding GPE handler 1c (acpiec)
> ...
> enabling GPE 18 (current: disabled) 00
> enabling GPE 1c (current: disabled) 00
> ...
>
> In that way when an acpi interrupt arrives, our right handler is called from
> [EMAIL PROTECTED] But it is *not* true. On my T23 the only interrupt I
> receive from acpi is from the power button, when I press it for more then 4
> seconds.
>
> Am I wrong about acpi interrupt mechanism? Should the right gpe handler be
> called *after* an acpi interrupt? What is the right value for sc_lastgpe, if
> my
> DSDT is not wrong?
>
> If I *experimentally* call on each kthread wakeup my 0x1c gpe handler, EC
> works
> fine, I can get all hotkey buttons, lid switches, hotplug and video events.
> Could we find a solution?
>
> Thanks to all.
>
> This is dmesg with *old* sc_lastgpe:
>
> OpenBSD 4.3-current (GENERIC) #118: Sun May 11 15:16:00 CEST 2008
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) III Mobile CPU 1133MHz ("GenuineIntel" 686-class)
> 1.14 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
> real mem = 1072721920 (1023MB)
> avail mem = 1029079040 (981MB)
> User Kernel Config
> UKC> disable apm
> 324 apm0 disabled
> UKC> quit
> Continuing...
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/18/06, BIOS32 rev. 0 @ 0xfd7e0,
> SMBIOS rev. 2.31 @ 0xe0010 (49 entries)
> bios0: vendor IBM version "1AET64WW (1.20 )" date 10/18/2006
> bios0: IBM 26474U2
> bios0: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-
> apm at bios0 function 0x15 not configured
> acpi0 at bios0: rev 2
> acpi0: tables DSDT FACP SSDT ECDT BOOT
> acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S4) PCI1(S4) DOCK(S4)
> USB0(S3) USB1(S3) USB2(S3) AC97(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpi device at acpi0 from table DSDT not configured
> acpi device at acpi0 from table FACP not configured
> acpi device at acpi0 from table SSDT not configured
> acpi device at acpi0 from table ECDT not configured
> acpi device at acpi0 from table BOOT not configured
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (PCI1)
> acpiec0 at acpi0
> acpicpu0 at acpi0: C3, C2, FVS, 1133, 733 MHz
> acpitz0 at acpi0: critical temperature 96 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> acpibat0 at acpi0: BAT0 model "IBM-02K7072" serial 434 type LION oem "SANYO"
> acpibat1 at acpi0: BAT1 not present
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock at acpi0 not configured
> bios0: ROM list: 0xc/0xe000 0xce000/0x1000 0xcf000/0x1000 0xdc000/0x4000!
> 0xe/0x1
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82830M Host" rev 0x04
> ppb0 at pci0 dev 1 function 0 "Intel 82830M AGP" rev 0x04
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "S3 SuperSavage" rev 0x05
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> agp0 at vga1: no integrated graphics
> uhci0 at pci0 dev 29 function 0 "Intel 82801CA/CAM
ACPI issue
Hi all.
I'm playing with acpi to get it working on my T23 thinkpad.
Thermal zone and battery status are working ok. But when I play with hotkey
buttons, open/close lid, unplug AC cable, nothing happens. After reading acpi.c
I've noted that this line is not correct for me (from [EMAIL PROTECTED]):
...
sc->sc_lastgpe = sc->sc_fadt->gpe0_blk_len << 2;
...
because I've a GPE on 0x18 and another on 0x1c, but sc_lastgpe value is 0x10.
Reading my acpidump output, I find:
...
Device(EC__) {
Name(_HID, 0x090cd041)
Name(_UID, 0x0)
Name(_GPE, 0x1c)
...
...
Scope(\_GPE) {
Method(_L18) {
^^
Store(\_SB_.PCI0.LPC_.EC__.HWAK, Local0)
...
If I change that line to:
...
sc->sc_lastgpe = ((sc->sc_fadt->gpe0_blk_len << 2) * 8) - 1;
...
(from acpica-unix version, found on netbsd source code), I don't know what I'm
doing, but it works. I can see these lines in dmesg:
...
Adding GPE handler 18 (level)
...
Adding GPE handler 1c (acpiec)
...
enabling GPE 18 (current: disabled) 00
enabling GPE 1c (current: disabled) 00
...
In that way when an acpi interrupt arrives, our right handler is called from
[EMAIL PROTECTED] But it is *not* true. On my T23 the only interrupt I
receive from acpi is from the power button, when I press it for more then 4
seconds.
Am I wrong about acpi interrupt mechanism? Should the right gpe handler be
called *after* an acpi interrupt? What is the right value for sc_lastgpe, if my
DSDT is not wrong?
If I *experimentally* call on each kthread wakeup my 0x1c gpe handler, EC works
fine, I can get all hotkey buttons, lid switches, hotplug and video events.
Could we find a solution?
Thanks to all.
This is dmesg with *old* sc_lastgpe:
OpenBSD 4.3-current (GENERIC) #118: Sun May 11 15:16:00 CEST 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) III Mobile CPU 1133MHz ("GenuineIntel" 686-class)
1.14 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 1072721920 (1023MB)
avail mem = 1029079040 (981MB)
User Kernel Config
UKC> disable apm
324 apm0 disabled
UKC> quit
Continuing...
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/18/06, BIOS32 rev. 0 @ 0xfd7e0, SMBIOS
rev. 2.31 @ 0xe0010 (49 entries)
bios0: vendor IBM version "1AET64WW (1.20 )" date 10/18/2006
bios0: IBM 26474U2
bios0: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-
apm at bios0 function 0x15 not configured
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT ECDT BOOT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S4) PCI1(S4) DOCK(S4)
USB0(S3) USB1(S3) USB2(S3) AC97(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpi device at acpi0 from table DSDT not configured
acpi device at acpi0 from table FACP not configured
acpi device at acpi0 from table SSDT not configured
acpi device at acpi0 from table ECDT not configured
acpi device at acpi0 from table BOOT not configured
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (PCI1)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, FVS, 1133, 733 MHz
acpitz0 at acpi0: critical temperature 96 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "IBM-02K7072" serial 434 type LION oem "SANYO"
acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock at acpi0 not configured
bios0: ROM list: 0xc/0xe000 0xce000/0x1000 0xcf000/0x1000 0xdc000/0x4000!
0xe/0x1
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82830M Host" rev 0x04
ppb0 at pci0 dev 1 function 0 "Intel 82830M AGP" rev 0x04
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "S3 SuperSavage" rev 0x05
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: no integrated graphics
uhci0 at pci0 dev 29 function 0 "Intel 82801CA/CAM USB" rev 0x02: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801CA/CAM USB" rev 0x02: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801CA/CAM USB" rev 0x02: irq 11
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x42
pci2 at ppb1 bus 2
cbb0 at pci2 dev 0 function 0 "TI PCI1420 CardBus" rev 0x00: irq 11
cbb1 at pci2 dev 0 function 1 "TI PCI1420 CardBus" rev 0x00: irq 11
"AT&T/Lucent LTMODEM" rev 0x01 at pci2 dev 2 function 0 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x42, i82562: irq 11,
address 00:d0:59:d8:07:09
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cards
Re: mrxvt and ksh issue [solved]
Thanks. I run -current, so ports are in sync with cvs. Patch to mantainer. But. But I noted we should investigate on child processes. I killed connection in our usual way (sigh!) with 4 tab opened. *One* of these had top running. All ksh were killed, *but* top's ksh not. Why? After 'ps l' WCHAN is ttyin, and STATE IE+, which (from man ps) indicate : * "IMarks a process that is idle (sleeping for longer than about 20 seconds)" * "EThe process is trying to exit" * "+The process is in the foreground process group of its control terminal" Keep investigating? On 01/05/08 04:50 +0200, Jesus Sanchez wrote: > Hi, I have just compiled and tested the program and I hopefully can say, > its really working. I never expected such interest by solving this > problem so I started loosing the hope. > > Thanks to the patch of Cesare Gargano, now I can run mrxvt using ksh > and then kill X with Ctrl+Alt+Backspace without leaving zombie/dead ksh > processes. I have a copy of the compiled binary mrxvt OpenBSD 4.2 on: > > http://usuarios.lycos.es/openminds/downloads/openbsderos/mrxvt_ksh > > (you have to install mrxvt by ports or packages, and then copy mrxvt_ksh > to the original mrxvt bin destination) > > This compiled binary works. But I had a little problems because (I > think) I have a different ports tree and the diff file does not worked > for me and I had to patch init.c by hand. After all the make process > stops telling me the line containing "rxvt_msg(..." made problems so I > commented it and then "make install" compiled a sane mrxvt (I think). > > The mrxvt dev team should be informed about all this stuff so the would > be able to make a fix of this without problems. > > Thanks Cesare. > -Jesus > > Cesare Gargano escribis: > >On 30/04/08 00:38 +0200, Jesus Sanchez wrote: > > > >>Solved! Oh my god, I'm so dumb and idiot, the option -hold was not > >>helping me > >>because I was using it in the wrong way, I used "-hold 0" and "-hold > >>false" and > >>I did not relized what the good option was "-hold 0x00" for the byte > >>order. > >> > >>Many thanks for your info and so sorry about the confusion, I really > >>feel as a dumb > >>newbie. > >> > >>Thanks for all. > >> > >> > >>Antoine Jacoutot escribis: > >> > >>>On Wed, 23 Apr 2008, Jesus Sanchez wrote: > >>> > >>> > >>>>I launch startx (with fvwm2 and mrxvt on my .xinitrc) as a regular user > >>>>(it's in the wheel group) and then I open a few tabs on mrxvt (3 or 4), > >>>>then I close X with Ctrl+Alt+Backspace and I found with 'ps -ax' that > >>>>the ksh opened with mrxvt (ttyp0, ttyp1, and more) are still running, > >>>>not mrxvt. > >>>> > >>>> > >>>Hi. > >>> > >>>Sorry, a bit late on this but I've been busy. > >>>Did you have a look at the '-hold' option? > >>>>From what you've been saying, disabling it should solve your problem. > >>> > >>> > >>>-hold mask > >>> Hold the tab open after the child process in it exits. mask > >>> is the > >>> mask of flags which control weather the tab will be held open > >>> based > >>> on the exit status of the child process. If the lowest bit > >>> (0x01) > >>> of mask is set, then the tab will always be held open after the > >>> child exits. If the next bit (0x02) is set, then the tab will > >>> only > >>> be held open if the child exits abnormally (e.g. via > >>> abort(1)). If > >>> the third bit (0x04) is set, then the tab will be held open if > >>> the > >>> child exits with non-zero status. > >>> > >>> NOTE: In previous versions of mrxvt this was a boolean option. > >>> For > >>> backward compatibility, the value of True, On, Yes will be > >>> treated > >>> as 1 and anything illegal will be treated as 0. The default is > >>> 0x06. [holdExit] > >>> > >> > > > >I try -hold option before other things, but this don'
Re: mrxvt and ksh issue [solved]
On 30/04/08 00:38 +0200, Jesus Sanchez wrote:
> Solved! Oh my god, I'm so dumb and idiot, the option -hold was not
> helping me
> because I was using it in the wrong way, I used "-hold 0" and "-hold
> false" and
> I did not relized what the good option was "-hold 0x00" for the byte order.
>
> Many thanks for your info and so sorry about the confusion, I really
> feel as a dumb
> newbie.
>
> Thanks for all.
>
>
> Antoine Jacoutot escribis:
> >On Wed, 23 Apr 2008, Jesus Sanchez wrote:
> >
> >>I launch startx (with fvwm2 and mrxvt on my .xinitrc) as a regular user
> >>(it's in the wheel group) and then I open a few tabs on mrxvt (3 or 4),
> >>then I close X with Ctrl+Alt+Backspace and I found with 'ps -ax' that
> >>the ksh opened with mrxvt (ttyp0, ttyp1, and more) are still running,
> >>not mrxvt.
> >>
> >
> >Hi.
> >
> >Sorry, a bit late on this but I've been busy.
> >Did you have a look at the '-hold' option?
> >>From what you've been saying, disabling it should solve your problem.
> >
> >
> > -hold mask
> > Hold the tab open after the child process in it exits. mask is
> > the
> > mask of flags which control weather the tab will be held open
> > based
> > on the exit status of the child process. If the lowest bit
> > (0x01)
> > of mask is set, then the tab will always be held open after the
> > child exits. If the next bit (0x02) is set, then the tab will
> > only
> > be held open if the child exits abnormally (e.g. via abort(1)).
> > If
> > the third bit (0x04) is set, then the tab will be held open if
> > the
> > child exits with non-zero status.
> >
> > NOTE: In previous versions of mrxvt this was a boolean option.
> > For
> > backward compatibility, the value of True, On, Yes will be
> > treated
> > as 1 and anything illegal will be treated as 0. The default is
> > 0x06. [holdExit]
>
>
I try -hold option before other things, but this don't work for me... I
try with different wm (fvwm, twm, cwm, e17, e16, gnome, xfce), but if I
kill x connection with ctrl+alt+backspace, all ksh remain alive.
I've added a IO handler to wrxvt init.c, this - as workaround - solve
all our issues.
If this is not necessary, post your config here, please.
--- src/init.c.orig Wed Apr 30 15:55:42 2008
+++ src/init.c Wed Apr 30 16:08:59 2008
@@ -46,6 +46,7 @@
intrxvt_getdtablesize ();
#endif
intrxvt_xerror_handler(const Display*, const XErrorEvent*);
+intrxvt_xioerror_handler (Display*);
void rxvt_init_colors (rxvt_t*);
void rxvt_init_win_size (rxvt_t*);
void rxvt_color_aliases (rxvt_t*, int);
@@ -886,6 +887,25 @@ rxvt_init_secondary(rxvt_t *r)
#endif
}
+/*
+ * FIXME
+ *
+ * Wed Apr 30 14:35:33 CEST 2008 +gar <[EMAIL PROTECTED]>
+ *
+ * This is a workaround for for OpenBSD users. On killed connection after
+ * ctrl+alt+backspace with ksh as default shell child processes don't exit,
+ * remaining in WCHAN state for ttyin. This works for me, I set a IO error
+ * handler for killed connection (man XSetErrorHandler) to clean vts before
+ * exiting.
+ */
+int
+rxvt_xioerror_handler(Display *d)
+{
+rxvt_msg(DBG_ERROR, DBG_INIT, "IO error, cleaning...\n");
+rxvt_Exit_signal(1);
+return 0;
+//abort();
+}
/* INTPROTO */
int
@@ -1079,6 +1099,7 @@ rxvt_init_resources(rxvt_t* r, int argc, const char *c
* allowed.
*/
XSetErrorHandler( (XErrorHandler) rxvt_xerror_handler );
+XSetIOErrorHandler( rxvt_xioerror_handler );
/* Initialize all atoms after establishing connection to X */
for (i = 0; i < NUM_XA; i++)
Re: mrxvt and ksh issue
On 24/04/08 21:13 +0200, Jesus Sanchez wrote: > Hi, thanks for your info. > > If I do the exit command on every tab, this thing doesn't happens, its > directly related with the key combination Ctrl+Alt+Backspace but I still > think this is a buggy behaviour ( in my opinion) and such thing should > be solved. > > To not get this in mind I moved to use rxvt and urxvt :S I know it's not > the solution but these zombie processes wich make me unable to halt the > machine are really disturbing to me. > > Jesus- > > > Clint Pachl escribis: > >Jesus Sanchez wrote: > >>Hi, I'm using 4.2. > > > >I'm using 4.1. > > > >> > >>I have installed from ports the program mrxvt it works well as people > >>say but I have (I believe) found a buggy behaviour when using mrxvt and > >>ksh (the OpenBSD one). > >> > >>I launch startx (with fvwm2 and mrxvt on my .xinitrc) as a regular user > >>(it's in the wheel group) and then I open a few tabs on mrxvt (3 or 4), > >>then I close X with Ctrl+Alt+Backspace and I found with 'ps -ax' that > >>the ksh opened with mrxvt (ttyp0, ttyp1, and more) are still running, > >>not mrxvt. > > > >I am also using fvwm2, but I use xdm instead of startx. I used to have > >the same problem you describe and I can't remember what I did to fix it. > > > >In my ~/.Xdefaults I have the line: > >mrxvt.macro.Primary+Ctrl+W: Close 0 > > > >I only have that because it matches the shortcut to close a tab in my > >Seamonkey browser. > > > >Also, I'm not sure if I installed from ports. OpenBSD didn't have an > >mrxvt port for quite awhile so I always compiled my own. Here are the > >characteristics of my current mrxvt: > > > >[EMAIL PROTECTED] mrxvt -h > >Mrxvt v0.5.2 > >Options: XPM,Jpeg,PNG,transparent,fade,tint,utmp,menubar,XIM, > >scrollbars=rxvt+NeXT+xterm+sgi+plain,xft,frills,linespace,selectionscrolling, > > > > > >256colour,cursorBlink,pointerBlank,session management,Resources > > > >> > >>When I try to kill them this doesn't works and ps return the "Is+" STATE > >>I get 0wn3d and then try (as root) kill -9 and still doesn't > >>works, ps returns "IEs+" STATE. Even If I have to power off the > >>computer with 'halt -p' these ksh sessions make it imposible, I have to > >>use 'halt -p -q'. > > > >What happens when you type the exit command instead of using the > >keyboard shortcut to close a tab/terminal? I wish I could remember > >what I did to fix the problem, but I also found this interesting line > >in my ~/.Xdefaults that may help: > > > >mrxvt.holdExit: 0x00 > > > >> > >>This stuff doesn't happends with tcsh and mrxvt. And also if I use rxvt > >>instead of mrxvt this also doesn't happends with ksh. > >> > >>I have not added my dmesg or something else because I really don't know > >>if it's necessary. > > > >You may also want to try the mrxvt mailing lists. I'm subscribed and > >they seem very active. The lead developer is top notch. > > > >-pachl > > Why do you want to quick with Ctrl+Alt+Backspace? ddTry to close your mrxvt *before* you press Ctrl+Alt+Backspace, this *should be* a safe way... But this, as you said, don't solve the problem... If I kill x server with Ctrl+Alt+Backspace without closing mrxvt window, ksh (and only ksh, because csh/tcsh works...) doesn't exit. I can kill these sleeping ksh, but what is locked (from mrxvt), I think, is utmp. If I try to w, my system doesn't respond. I'm investigating...
Re: aterm, rxvt -- memory usage
On 21/04/08 17:04 -0700, Clint Pachl wrote: Jesus Sanchez wrote: Hi all, I'm using 4.2 without problem, and I'm trying to find one "xterm" to my personal use with only one thing in mind: low cpu and memory usage. I have been using mrxvt for years. It's also "multi-tabbed". Currently, I'm running 10 terminals in a single mrxvt process and it is currently using Size: 2644K, and Res: 4472K and barely touches the CPU. I'm running a custom compiled version with all the fancy features turned off. It is extremely fast and reliable; I haven't found anything faster. -pachl Yes, I agree. mrxvt is simple and fast. Try it.
dropping ieee80211 frames
Hi all, can i find a way of blocking *all* ieee80211 frames without modifying kernel source? Thanks.
