Re: looking for arping or equivalent tool
Claude Jones writes: Arping was a useful tool that was discontinued during the RHEL5 lifecycle and I have not been able to find an installable equivalent for Fedora 14 due to glibc dependencies. Does anyone know of a tool that can broadcast an ARP announcement saying this IP should resolve to this MAC” and let you specify both Fedora 14 includes arping. Package iputils-20100418-3.fc14.i686 provides /sbin/arping and creates /usr/sbin/arping as a symlink to it. -- Dick St. Peters, stpet...@netheaven.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
memmove() with 5 arguments? (was F14 X server problem)
On Sun, 28 Nov 2010 19:33:54 -0500 I started this topic by saying: I need to run X with the fvwm window manager, but the F14 X server doesn't play nice with fvwm - or with twm. When fvwm or twm calls XCreateFontSet(), the X server dies with a SIGSEGV. To get around this, I have copied the F13 /usr/bin/Xorg server binary and /usr/lib/xorg/modules directory contents to my F14 system, and they work just fine with the F14 fvwm, F14 X libraries, and F14 fonts. While this workaround works, it's not exactly a good long term fix. Note that this workaround means the problem is with the F14 X server or its loadable modules, not the F14 fvwm. When twm is used, it calls XCreateFontSet() with a base_font_name_list argument different from that in the fvwm XCreateFontSet() call, and the F14 server dies, so the problem is not the font asked for by fvwm. This gets stranger and stranger ... Before trying to dig into the X server code, I wanted some clues about where to look, so I put this into root's .xserverrc: #!/bin/sh exec /usr/bin/ltrace /usr/bin/Xorg :0 I deleted root's .xinitrc, .fvwmrc, and .fvwm directory and, as root (only root can ltrace /usr/bin/Xorg) I ran: xinit fvwm 2/tmp/Xorg.out The ltrace output in /tmp/Xorg.out has 176 calls to memmove(), all with five arguments, like this example: memmove(0xa352c50, 0xa3535e0, 1648, 0x806892f, 0x40001c) Can anyone shed some light on what is going on here? The first three arguments appear to be the usual three memmove() arguments: dest, src, and count. The extra two aren't documented anywhere I can find, and memmove() has always been a three-argument function. To further confuse things, memmove() isn't the only call with too many arguments. clock_gettime() is supposed to have two arguments, but it's called 694 times with five arguments. There may well be other calls with strange argument counts, but the output has 371800 lines, and I'm not up to examining all of them. -- Dick St. Peters, stpet...@netheaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: memmove() with 5 arguments? (was F14 X server problem)
Nalin Dahyabhai writes: On Mon, Nov 29, 2010 at 04:37:05PM -0500, Dick St. Peters wrote: The ltrace output in /tmp/Xorg.out has 176 calls to memmove(), all with five arguments, like this example: memmove(0xa352c50, 0xa3535e0, 1648, 0x806892f, 0x40001c) Can anyone shed some light on what is going on here? The first three arguments appear to be the usual three memmove() arguments: dest, src, and count. The extra two aren't documented anywhere I can find, and memmove() has always been a three-argument function. It looks to me as though ltrace just doesn't know how many arguments memmove() takes, and this can be fixed with a quick change to /etc/ltrace.conf. I went ahead and opened bug #658311 about it. Thank you for the explanation. I'm relieved that there is one. I didn't know ltrace got the arg counts and types from a conf file, but I see /etc/ltrace.conf is mentioned in the ltrace man page. Now I can go back to pursuing why /usr/bin/Xorg dies. -- Dick St. Peters, stpet...@netheaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
F14 X server problem
I need to run X with the fvwm window manager, but the F14 X server doesn't play nice with fvwm - or with twm. When fvwm or twm calls XCreateFontSet(), the X server dies with a SIGSEGV. To get around this, I have copied the F13 /usr/bin/Xorg server binary and /usr/lib/xorg/modules directory contents to my F14 system, and they work just fine with the F14 fvwm, F14 X libraries, and F14 fonts. While this workaround works, it's not exactly a good long term fix. Note that this workaround means the problem is with the F14 X server or its loadable modules, not the F14 fvwm. When twm is used, it calls XCreateFontSet() with a base_font_name_list argument different from that in the fvwm XCreateFontSet() call, and the F14 server dies, so the problem is not the font asked for by fvwm. -- Dick St. Peters, stpet...@netheaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F14 X server problem
Tom Horsley writes: On Sun, 28 Nov 2010 19:33:54 -0500 Dick St. Peters wrote: I need to run X with the fvwm window manager, but the F14 X server doesn't play nice with fvwm I use fvwm all the time, I've never had the X server die on me. Maybe you have something in your .fvwmrc file that refers to some specific font for titles or menus or something that the X server finds offensive? (Not that it should crash). Well, the F13 X server copied to and running on my F14 system does not mind anything the F14 fvwm does with the same .fvwmrc and fonts (and libraries). Also, the F14 fvwm with the same .fvwmrc and fonts works fine with the F14 Xvnc. Let's be precise: you are using the F14-distributed fvwm with the F14-distributed /usr/bin/Xorg server, and it's working? In other words: $ rpm -qa | egrep 'fvwm|xorg-x11-server-Xorg' fvwm-2.5.30-2.fc14.i686 xorg-x11-server-Xorg-1.9.1-3.fc14.i686 -- Dick St. Peters, stpet...@netheaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F14 X server problem
Tom Horsley writes: On Sun, 28 Nov 2010 20:33:35 -0500 Dick St. Peters wrote: Let's be precise: you are using the F14-distributed fvwm with the F14-distributed /usr/bin/Xorg server, and it's working? In other words: $ rpm -qa | egrep 'fvwm|xorg-x11-server-Xorg' fvwm-2.5.30-2.fc14.i686 xorg-x11-server-Xorg-1.9.1-3.fc14.i686 Almost, I'm using the 64 bit versions: xorg-x11-server-Xorg-1.9.1-3.fc14.x86_64 fvwm-2.5.30-2.fc14.x86_64 I've got my own highly customized .fvwmrc file, but I don't customize any fonts in it, so I'm getting whatever fvwm uses as defaults for fonts. My normal .fvwmrc is highly customized, including some font sizes, but I got the same problem with Xorg dieing when running as a user with no .fvwmrc at all. That was one of my early experiments when I began fighting with this problem after the F13 - F14 upgrade. -- Dick St. Peters, stpet...@netheaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
