Re: 6.0 RC1 usbd.conf (and installation comments)
Le Mercredi 26 Octobre 2005 02:46, Joel Hatton a écrit : > most files in /etc/rc.d changed, so installing them all with > mergemaster was laborious - a note in UPDATING similar to that for > 5.x: > > "The simplest solution is an 'rm -rf /etc/rc.d/*' and then > 'mergemaster -i'." Yes but be carefull, by sample amavisd-new uses scripts in /etc/rc.d and not in /usr/local/etc/rc.d. "Why the mail server does not work anymore ?" Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
On Thu, 27 Oct 2005 09:31, James Long wrote: > > wicontrol is obsolete and you should not need to use it, particularly > > for ath(4) devices. Why are you using it? Is some feature you need > > missing from ifconfig? > > The command I use most is wicontrol -L Try ifconfig ath0 list scan -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpSE5NRXD8b9.pgp Description: PGP signature
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
> On 2005-10-26, Mark Andrews wrote: > > Leading zeros are ambigious. Some platforms treat them as octal > > others treat them as decimal. > > There is nothing ambiguous about the example provided. (Perhaps > it wasn't a good example, but it's always a bug if '04' is not > correctly decoded, regardless of the numeric base in use.) You want a ambigious example? 192.168.222.012 Seen this sort of thing in real life when the admin wanted to make the file look pretty and they wanted 12 for the last octet not 10. Seen boxes that used %03u.%03u.%03u.%03u to print out the octets. It's much easier to just reject octal and hexadecimal than to work out when and when not it is ambigious. It is also better to demand all 4 octets. It also generates less support complaints. Mark > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
On 2005-10-26, Matt Emmerton wrote: > > On 2005-10-26, Mark Andrews wrote: > > > Leading zeros are ambigious. Some platforms treat them as octal > > > others treat them as decimal. > > > > There is nothing ambiguous about the example provided. (Perhaps > > it wasn't a good example, but it's always a bug if '04' is not > > correctly decoded, regardless of the numeric base in use.) > > Not to belittle the point, but '04' is invalid for base-2/3/4. The bases discussed here were 8 and 10; my comment applied to them. As for base 3, I don't care what you write using it, I won't be bothering about it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
> wicontrol is obsolete and you should not need to use it, particularly > for ath(4) devices. Why are you using it? Is some feature you need > missing from ifconfig? The command I use most is wicontrol -L ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
> On 2005-10-26, Mark Andrews wrote: > > Leading zeros are ambigious. Some platforms treat them as octal > > others treat them as decimal. > > There is nothing ambiguous about the example provided. (Perhaps > it wasn't a good example, but it's always a bug if '04' is not > correctly decoded, regardless of the numeric base in use.) Not to belittle the point, but '04' is invalid for base-2/3/4. -- Matt Emmerton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
On Wed, Oct 26, 2005 at 03:20:47PM -0700, James Long wrote: > wicontrol.c defaults to the "wi" interface. I used to have a > wi device, but it eventually took a dump and I bought a new > ath-based card, which works flawlessly AFAIK, after four months > or so. > > But I grow weary of having to specify "-i ath0" every time I > run wicontrol. > > Please review the following patch to /usr/src/usr.sbin/wicontrol/wicontrol.c > which modifies wicontrol to look for an environment variable > WI_IFACE and if set, take the interface name from that variable. > If unset, the interface name defaults to "wi0" just as before, > which hopefully will make this POLA compliant. Googling for > "WI_IFACE" I find no indications that this variable name already > is in use for anything else. > > Apologies in advance for the simple diff output patch. wicontrol is obsolete and you should not need to use it, particularly for ath(4) devices. Why are you using it? Is some feature you need missing from ifconfig? -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpBDY3g7ydnF.pgp Description: PGP signature
RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
wicontrol.c defaults to the "wi" interface. I used to have a
wi device, but it eventually took a dump and I bought a new
ath-based card, which works flawlessly AFAIK, after four months
or so.
But I grow weary of having to specify "-i ath0" every time I
run wicontrol.
Please review the following patch to /usr/src/usr.sbin/wicontrol/wicontrol.c
which modifies wicontrol to look for an environment variable
WI_IFACE and if set, take the interface name from that variable.
If unset, the interface name defaults to "wi0" just as before,
which hopefully will make this POLA compliant. Googling for
"WI_IFACE" I find no indications that this variable name already
is in use for anything else.
Apologies in advance for the simple diff output patch.
Jim
t21 : 15:13:58 /usr/src/usr.sbin/wicontrol# diff wicontrol.c.orig wicontrol.c
1092c1092,1094
< iface = "wi0";
---
> if ((iface = getenv("WI_IFACE")) == NULL) {
> iface = "wi0";
> }
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
On 2005-10-26, Mark Andrews wrote: > Leading zeros are ambigious. Some platforms treat them as octal > others treat them as decimal. There is nothing ambiguous about the example provided. (Perhaps it wasn't a good example, but it's always a bug if '04' is not correctly decoded, regardless of the numeric base in use.) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 RC1 usbd.conf (and installation comments)
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote: > /etc/usbd.conf has lost the [Device] configuration for the mouse, > which although doesn't prevent the mouse from working, it did mean > that I had to add those lines again so that I could turn on '-z > 4' for the scroll wheel. If this was the wrong way to do it, let > me know - adding this item to the moused_flags didn't work. I'm > actually wondering if this shouldn't be the default nowadays - > what standard usb mouse _doesn't_ have one? The entry is now in devd.conf. I do agree we should think about making -z the default (at least in the config files). > DHCP configuration - for some reason my machine didn't acquire a > default route on boot, but rerunning the dhclient script after > boot caused the interface to be set up again successfully. I > haven't looked into this further yet, I'll repost if it is a > repeatable problem. Odd, let me know if this happens again. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpnUI38euhOH.pgp Description: PGP signature
Re: Strange crashing/rebooting problem
On Wed, Oct 26, 2005 at 01:05:04AM -0400, Bryan Fullerton wrote: > ... > You didn't mention, have you run Dell diagnostics on the machine to > rule out hardware issues? While those diagnostics may well demostrate that a problem exists, the lack of a problme is not demonstrated by a machine passing all diagnostics. In particular, on a previous Dell i5000e laptop, it was not until 8 days before the warranty expired that I discovered conclusive evidence that the (DB-9M) serial port did not work at all. This, despite passing Dell's diagnostics with flying colors. And this was because the diagnostics -- from what I can guess -- did not attempt to actually transmit or receive data via the serial port. So: by all means, use the diagnostics, but use a suitably-sized "grain of salt" in evaluating the results. Peace, david -- David H. Wolfskill [EMAIL PROTECTED] Prediction is difficult, especially if it involves the future. -- Niels Bohr See http://www.catwhisker.org/~david/publickey.gpg for public key. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATA RAID problem in 6.0-RC1 (ata_alloc_request/ata_raid_init_request)
I've been seeing a number of strange messages in my log since updating to 6.0-RC1. Usually they happen when some intense disk access is happening (e.g. when /etc/periodic/security/100.chksetuid is running at 03:01), but it doesn't happen _every_ morning, and it doesn't always happen if I manually run the script. It also occasionally happens at times where I wouldn't say I was doing much with the disk. I'm hoping nothing bad is happening to my data. At least, fsck doesn't mention any problems, and I haven't noticed any corruption yet... I'm on an AMD64 system, with an MSI K8T-Neo2 motherboard. ATA-related dmesg: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RC1 #0: Wed Oct 12 21:05:06 BST 2005 [EMAIL PROTECTED]:/usr/obj/repo/FreeBSD/FreeBSD-6.x/src/sys/OUTCOLD ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3500+ (2200.10-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) avail memory = 1027952640 (980 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) ... atapci0: port 0xec00-0xec7f,0xe800-0xe8ff mem 0xcfffb000-0xcfffbfff,0xcffc-0xcffd irq 17 at device 13.0 on pci0 ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 atapci1: port 0xc800-0xc807,0xc400-0xc403,0xc000-0xc007,0xbc00-0xbc03,0xb800-0xb80f,0xb400-0xb4ff irq 20 at device 15.0 on pci0 ata5: on atapci1 ata6: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci2 ata1: on atapci2 ... ad0: 32634MB at ata0-master UDMA66 acd0: DVDR at ata1-master UDMA33 ad4: 156334MB at ata2-master SATA150 ad6: 156334MB at ata3-master SATA150 ar0: 156334MB status: READY ar0: disk0 READY (master) using ad6 at ata3-master ar0: disk1 READY (mirror) using ad4 at ata2-master atacontrol output: # atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 4 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI revision 0 Slave: no device present ATA channel 2: Master: ad4 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: ad6 Serial ATA v1.0 Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present ATA channel 6: Master: no device present Slave: no device present # atacontrol status ar0 ar0: ATA RAID1 subdisks: ad6 ad4 status: READY A sample of the error messages follows: Oct 25 21:20:21 outcold kernel: DOH! ata_alloc_request failed! Oct 25 21:20:23 outcold kernel: FAILURE - out of memory in ata_raid_init_request Oct 25 21:20:23 outcold last message repeated 131 times Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597617664, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597748736, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597961728, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598207488, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598453248, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598682624, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598895616, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599174144, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599452672, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599747584, length=16384)]error = 5 ... ... Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629107712, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629386240, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629648384, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: DOH! ata_alloc_request failed! Oct 25 21:20:53 outcold kernel: FAILURE - out of memory in ata_raid_init_request Oct 25 21:20:53 outcold last message repeated 146 times Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635156992, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635533824, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635992576, length=16384)]error = 5 ... ... etc If you need any more deatils, please let me know. -- David Taylor
Re: Strange crashing/rebooting problem
Taken from the digest form, so hopefully I won't whack the formatting too badly. Dan Charrois <[EMAIL PROTECTED]> wrote: [snip] >No, I haven't been able to run diagnostics and rule out the hardware >for two reasons.. First, the server is located about an hour's drive >away, and I haven't had the chance to get to it yet. Of course, this >can be fixed. But secondly, I have no idea *how* to run Dell >Diagnostics. The "Dell PowerEdge Service and Diagnostic Utilities, >Version 4.4" CD that I have insists on being run from Windows, right >down to a setup.exe in the root directory and a ReadMe that starts >describing how to use the CD as: > > [snip] This is pretty much classic Dell. We've purchased a number of systems without operating systems on which we run FreeBSD. However, they continually operate under the assumption that we are running Windoze or Linux, and expect those to do things like BIOS updates. I'm trying to work it out with them, but it's been pretty painful so far (enough that I'm starting to look at other hardware vendors). However, in the case of the diagnostics utilities, Dell's a bit more enlightened. These links ftp://ftp.dell.com/diags/ED5061A0.tar.gz ftp://ftp.dell.com/diags/EI5061A0.ZIP ftp://ftp.dell.com/diags/MP1038A0.tar.gz ftp://ftp.us.dell.com/diags/MP1038A0.zip point at the Dell 32-bit diagnostics (first pair) and the memory diagnostics utilities (second pair). The .tar.gz files containg raw floppy images suitable for writing to floppy with a command like cat file.img | dd of=/dev/fd0 obs=18k or something like that. The .ZIP files contain what appear to be ISO images suitable for burning to a CD. Figuring that command out is left as an exercise for the reader. :-) -- Alan Amesbury University of Minnesota ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADSUP: ddb stack trace command name changes
First, the 'traceall' command has been renamed to 'alltrace'. This allows
abbreviated versions of 'trace' such as 't' or 'tr' to work again. It is
also more consistent with other ddb functions that dump data about multiple
objects ('show allpcpu', etc.).
Secondly, 'bt' has been added as a new alias for 'trace' which should make
some gdb-using folks lives easier if they are used to using 'bt' in gdb all
the time.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make.conf for 6.0
On Mer 26 octobre 2005 15:43, Thomas T. Veldhouse wrote: > Chris wrote: > >>Ok thanks I already use it for ports, but just plain -O2 -pipe for the >>world and kernel. >> >> >> > Hmm ... I find this thread surprising, as this is the first I have heard > of FreeBSD working correctly with -O2. So, is this the options > suggested for make.conf on x86? > > CFLAGS= -O2 -pipe -fno-strict-aliasing > COPTFLAGS= -O2 -pipe > this is not so surprising to me, i'm using these flags + -mcpu=pentium4 for about one year on 5-STABLE, following the suggestion of Kris Kennaway if i remember well. be happy, this day is the first day of the rest of your freebsd -O2 user life ! -- Matthieu Michaud - EPITA 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
> I don't know whether this is worth filing a PR for, but it seems the > resolver no longer likes leading zeroes in an IP4 address in /etc/hosts. > The change (in 5- ) appeared sometime in the last month or two. > > Personally I'm inclined to view this as a regression although it's > simple enough to work around. Leading zeros are ambigious. Some platforms treat them as octal others treat them as decimal. Mark > Cheers, > jan > > -- > jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ > Tel +44 (0)117 3317661 http://ioctl.org/jan/ > Unfortunately, I have a very good idea how fast my keys are moving. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Resolver doesn't like 1.2.3.04 in /etc/hosts
I don't know whether this is worth filing a PR for, but it seems the resolver no longer likes leading zeroes in an IP4 address in /etc/hosts. The change (in 5- ) appeared sometime in the last month or two. Personally I'm inclined to view this as a regression although it's simple enough to work around. Cheers, jan -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Unfortunately, I have a very good idea how fast my keys are moving. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make.conf for 6.0
Chris wrote: Ok thanks I already use it for ports, but just plain -O2 -pipe for the world and kernel. Hmm ... I find this thread surprising, as this is the first I have heard of FreeBSD working correctly with -O2. So, is this the options suggested for make.conf on x86? CFLAGS= -O2 -pipe -fno-strict-aliasing COPTFLAGS= -O2 -pipe Tom Veldhouse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: math/grace port: "libXcursor.so.1.0" not found ??
--- Peter Jeremy <[EMAIL PROTECTED]> wrote: > On Tue, 2005-Oct-25 20:41:33 -0700, Rob wrote: > >2. Create $HOME/.grace/gracerc.user and put > > one line in this file: > > USE "pow" TYPE f_of_dd FROM "/usr/lib/libm.so" > > (this is the example from the Grace UsersGuide) > > Does grace work correctly if you don't include this > line? Without that line, grace starts without any problem. With that line, grace cannot perform the action described in that line (USE "pow" FROM "libm.so"), because the responsible dlopen() call has the error: Shared object "libXcursor.so.1.0" not found, required by "xmgrace" However, despite this error, grace continues to start up fine (but, as I said, without loading the function from the library). Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: math/grace port: "libXcursor.so.1.0" not found ??
--- Pete French <[EMAIL PROTECTED]> wrote: > > I am the only FreeBSD user on the Grace > mailinglist. > > Apparently the dlopen() call in grace works fine > > on Linux and others. But not with FreeBSD. > > This is not a problem with the dlopen call *or* > freebsd - the problem is that it is asking for > a library 'libXcursor.so.1.0' which does not > exist on FreeBSD. There is a 'libXcursor.so.1' > though. You need to get the grace people to change > the application so it requests the correct > library when running on FreeBSD. The reason why the grace developper blames FreeBSD is because of this: The executable 'xmgrace' is linked to /usr/X11R6/lib/libX11.so.6 and 'strings /usr/X11R6/lib/libX11.so.6 | grep libXcursor' gives: libXcursor.so.1.0.2 So according to the grace developper, the reason for my problem is a problem with libX11.so.6. But I know nothing about this stuff By the way: can someone also explain to me why libX11.so.6 has the string "libXcursor.so.1.0.2". I will then forward this to the grace mailinglist, and tell them that there's something wrong with Grace. Thank so much! Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: math/grace port: "libXcursor.so.1.0" not found ??
On Tue, 2005-Oct-25 20:41:33 -0700, Rob wrote:
>2. Create $HOME/.grace/gracerc.user and put
> one line in this file:
> USE "pow" TYPE f_of_dd FROM "/usr/lib/libm.so"
> (this is the example from the Grace UsersGuide)
Does grace work correctly if you don't include this line?
>3. Start grace like this:
> $ xmgrace
> Shared object "libXcursor.so.1.0" not found,
> required by "xmgrace"
"libXcursor.so.1.0" is not a valid FreeBSD shared library name.
The closest is /usr/X11R6/lib/libXcursor.so.1
> handle =
>(void *)dlopen("/usr/lib/libm.so", RTLD_LAZY)
It doesn't make sense for an attempt to dlopen libm to complain about
an X library.
You might like to try asking the port maintainer (see the Makefile).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: math/grace port: "libXcursor.so.1.0" not found ??
> I am the only FreeBSD user on the Grace mailinglist. > Apparently the dlopen() call in grace works fine > on Linux and others. But not with FreeBSD. This is not a problem with the dlopen call *or* freebsd - the problem is that it is asking for a library 'libXcursor.so.1.0' which does not exist on FreeBSD. There is a 'libXcursor.so.1' though. You need to get the grace people to change the application so it requests the correct library when running on FreeBSD. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf and short packets
On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote: > On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote: > >> tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1 > >>34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > > >>127.0.0.1.643: . ack 30 win 65535 > >> 0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 > >> F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab > >> .)]. 0x0020: 5db7 f2f2 5010 7dce > >> ]...P...}... 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > >> > > >>127.0.0.1.643: . ack 30 win 65535 > >> 0x: 4600 002c d21d 4000 0306 a5ac 7f00 0001 > >> F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab > >> .)]. 0x0020: 5db7 f2f2 5010 7dce > >> ]...P...}... > >> > >>The rule for this packet is not a "log" one, but the sign (short) is > >>what i cannot understand. > > > > Read 'man 1 tcpdump' about key "-s". > > You command must be like "tcpdump -s 1000 -n -e -ttt -x -i pflog0 host > > 127.0.0.1" > > > > Change value 1000 to appropriate. > > Hi, and thanks for the replay, > but my question is not about how to use tcpdump (i know -s key), but > what to do with pf to make this packets pass through. > When my pf is up i cannot rsh to ipcad, but when it is down - everything > is working just fine. > I need this rsh to get my ip statistics. sorry, i misunderstand you. can you provide output 'pfctl -sr -g' (at leat sensitive rules before number 34) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange crashing/rebooting problem
On 10/25/05, Dan Charrois <[EMAIL PROTECTED]> wrote: Hi all. I'm wondering if anyone can shed some light on a strange crashing/rebooting problem I'm having. First, the specs: Hardware: Dell PowerEdge 2850 rack mounted server, Dual 3.4 Ghz Xeon, 5 Gb memory [snip] You didn't mention, have you run Dell diagnostics on the machine to rule out hardware issues? No, I haven't been able to run diagnostics and rule out the hardware for two reasons.. First, the server is located about an hour's drive away, and I haven't had the chance to get to it yet. Of course, this can be fixed. But secondly, I have no idea *how* to run Dell Diagnostics. The "Dell PowerEdge Service and Diagnostic Utilities, Version 4.4" CD that I have insists on being run from Windows, right down to a setup.exe in the root directory and a ReadMe that starts describing how to use the CD as: 1. Insert the Service and Diagnostic Utilities CD into the CD drive on a system running Windows. The setup program should start automatically. If it does not, click the Start button, click Run, and then type x:setup.exe (where x is the drive letter of your CD drive). This isn't a dual boot machine - it's sole task is running FreeBSD for an SQL server, so that's not an option for me. You'd think that they'd have a self-booting CD that would be able to diagnose the machine, since for the life of me, even if I *were* running Windows, I wouldn't be able to figure out how to diagnose a problem if part of the problem made Windows unbootable... I must be missing something. Dan -- Syzygy Research & Technology Box 83, Legal, AB T0G 1L0 Canada Phone: 780-961-2213 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf and short packets
dawnshade wrote: maybe this link help you.: http://groups.google.com/group/fido7.ru.unix.bsd/msg/187bf3d7de6e3eab?dmode=source Sorry to other subscribers - it in russian. short fix problem: replace 'pass quick all lo0' to 'pass qucik all allow-opts lo0' ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks alot! It is working now :) Best regards, Anton Nikiforov smime.p7s Description: S/MIME Cryptographic Signature
Re: make installworld failure
Alexander 'alxl' Lobachov wrote: Hello, Just cvsuped and built the kernel and installed it ok, buildworld went clear also, tried to installworld and got this: $ sudo make installworld mkdir -p /tmp/install.QhTsbtJk for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.QhTsbtJk; done cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=athlon-xp GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/legacy/usr/share/tmac PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.QhTsbtJk make -f Makefile.inc1 reinstall make: Permission denied *** Error code 126 Stop in /usr/src. *** Error code 1 Stop in /usr/src. The box was quite new actually, already running -STABLE maybe a few weeks old or so. Any hints how to fix it will be greatly appreciated. Thanks. /tmp must be mounted without *noexec* option. So your /etc/fstab must contain something like this /dev/ad0s1e /tmpufs rw,nosuid,nodev 22 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf and short packets
On Wednesday 26 October 2005 12:41, Anton Nikiforov wrote: > dawnshade wrote: > > On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote: > >> On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote: > tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1 > 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > > 127.0.0.1.643: . ack 30 win 65535 > 0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 > F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab > .)]. 0x0020: 5db7 f2f2 5010 7dce > ]...P...}... 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > > 127.0.0.1.643: . ack 30 win 65535 > 0x: 4600 002c d21d 4000 0306 a5ac 7f00 0001 > F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab > .)]. 0x0020: 5db7 f2f2 5010 7dce > ]...P...}... > > The rule for this packet is not a "log" one, but the sign (short) is > what i cannot understand. > >>> > >>>Read 'man 1 tcpdump' about key "-s". > >>>You command must be like "tcpdump -s 1000 -n -e -ttt -x -i pflog0 host > >>>127.0.0.1" > >>> > >>>Change value 1000 to appropriate. > >> > >>Hi, and thanks for the replay, > >>but my question is not about how to use tcpdump (i know -s key), but > >>what to do with pf to make this packets pass through. > >>When my pf is up i cannot rsh to ipcad, but when it is down - everything > >>is working just fine. > >>I need this rsh to get my ip statistics. > > > > sorry, i misunderstand you. > > can you provide output 'pfctl -sr -g' (at leat sensitive rules before > > number 34) > > Hello and thanks again for the replay. > Here is the output of pfctl -sr -g. > @0 scrub in all fragment reassemble >[ Skip steps: i=end f=end p=end sa=end sp=end da=end dp=end ] >[ queue: qname= qid=0 pqname= pqid=0 ] > @1 scrub out all random-id fragment reassemble >[ Skip steps: i=end d=end f=end p=end sa=end sp=end da=end dp=end ] >[ queue: qname= qid=0 pqname= pqid=0 ] > @0 pass quick on lo0 all >[ Skip steps: p=4 sp=802 da=2 dp=17 ] >[ queue: qname= qid=0 pqname= pqid=0 ] > I was "playing" with this rule and used to install it in different ways > and places. I have no idea what to do with this. > I was turning off scrubbing, everything beloew. With no result. > > All the rest is not about lo0, but here they are (34 out of 9849): > > @1 block drop in quick inet from 192.168.11.1 to any > @2 block drop in log quick on fxp0 inet from any to 224.0.0.0/3 > @3 block drop out log quick on fxp0 inet from 224.0.0.0/3 to any > @4 block drop in log quick on fxp0 inet proto tcp all flags FPU/FPU > @5 block drop in log quick on fxp0 inet proto tcp all flags FS/FSRA > @6 block drop in log quick on fxp0 inet proto tcp all flags /FSRA > @7 block drop in log on fxp0 proto tcp all > @8 block drop in log on fxp0 proto udp all > @9 block drop out log on fxp0 proto tcp all > @10 block drop out log on fxp0 proto udp all > @11 block drop in log on fxp0 proto icmp all > @12 block drop out log on fxp0 proto icmp all > @13 block return-rst in log on fxp0 proto tcp all > @14 block return-rst out log on fxp0 proto tcp all > @15 block return-icmp(port-unr, port-unr) in log on fxp0 proto udp all > @16 block return-icmp(port-unr, port-unr) out log on fxp0 proto udp all > @17 block drop in log on fxp0 proto tcp from any to any port = pop3 > @18 block drop in log on fxp0 proto tcp from any to any port = loc-srv > @19 block drop in log on fxp0 proto tcp from any to any port = profile > @20 block drop in log on fxp0 proto tcp from any to any port = netbios-ns > @21 block drop in log on fxp0 proto tcp from any to any port = netbios-dgm > @22 block drop in log on fxp0 proto tcp from any to any port = netbios-ssn > @23 block drop in log on fxp0 proto tcp from any to any port = microsoft-ds > @24 block drop in log on fxp0 proto udp from any to any port = pop3 > @25 block drop in log on fxp0 proto udp from any to any port = loc-srv > @26 block drop in log on fxp0 proto udp from any to any port = profile > @27 block drop in log on fxp0 proto udp from any to any port = netbios-ns > @28 block drop in log on fxp0 proto udp from any to any port = netbios-dgm > @29 block drop in log on fxp0 proto udp from any to any port = netbios-ssn > @30 block drop in log on fxp0 proto udp from any to any port = microsoft-ds > @31 block drop out log on fxp0 proto tcp from any to any port = pop3 > @32 block drop out log on fxp0 proto tcp from any to any port = loc-srv > @33 block drop out log on fxp0 proto tcp from any to any port = profile > @34 block drop out log on fxp0 proto tcp from any to any port = netbios-ns > > Just in case: > # pfctl -sr -g | grep lo0 > @0 pass quick on lo0 all maybe this link help you.: http://groups.google.com/group/fido7.ru.unix.bsd/msg/187bf3d7de6e3eab?dmode=source Sorry to other subscribers - it in russian. short fix problem: replace 'pass quick all lo0' to 'pass qucik all
Re: pf and short packets
dawnshade wrote: On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote: On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote: tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > 127.0.0.1.643: . ack 30 win 65535 0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab .)]. 0x0020: 5db7 f2f2 5010 7dce ]...P...}... 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 127.0.0.1.643: . ack 30 win 65535 0x: 4600 002c d21d 4000 0306 a5ac 7f00 0001 F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab .)]. 0x0020: 5db7 f2f2 5010 7dce ]...P...}... The rule for this packet is not a "log" one, but the sign (short) is what i cannot understand. Read 'man 1 tcpdump' about key "-s". You command must be like "tcpdump -s 1000 -n -e -ttt -x -i pflog0 host 127.0.0.1" Change value 1000 to appropriate. Hi, and thanks for the replay, but my question is not about how to use tcpdump (i know -s key), but what to do with pf to make this packets pass through. When my pf is up i cannot rsh to ipcad, but when it is down - everything is working just fine. I need this rsh to get my ip statistics. sorry, i misunderstand you. can you provide output 'pfctl -sr -g' (at leat sensitive rules before number 34) Hello and thanks again for the replay. Here is the output of pfctl -sr -g. @0 scrub in all fragment reassemble [ Skip steps: i=end f=end p=end sa=end sp=end da=end dp=end ] [ queue: qname= qid=0 pqname= pqid=0 ] @1 scrub out all random-id fragment reassemble [ Skip steps: i=end d=end f=end p=end sa=end sp=end da=end dp=end ] [ queue: qname= qid=0 pqname= pqid=0 ] @0 pass quick on lo0 all [ Skip steps: p=4 sp=802 da=2 dp=17 ] [ queue: qname= qid=0 pqname= pqid=0 ] I was "playing" with this rule and used to install it in different ways and places. I have no idea what to do with this. I was turning off scrubbing, everything beloew. With no result. All the rest is not about lo0, but here they are (34 out of 9849): @1 block drop in quick inet from 192.168.11.1 to any @2 block drop in log quick on fxp0 inet from any to 224.0.0.0/3 @3 block drop out log quick on fxp0 inet from 224.0.0.0/3 to any @4 block drop in log quick on fxp0 inet proto tcp all flags FPU/FPU @5 block drop in log quick on fxp0 inet proto tcp all flags FS/FSRA @6 block drop in log quick on fxp0 inet proto tcp all flags /FSRA @7 block drop in log on fxp0 proto tcp all @8 block drop in log on fxp0 proto udp all @9 block drop out log on fxp0 proto tcp all @10 block drop out log on fxp0 proto udp all @11 block drop in log on fxp0 proto icmp all @12 block drop out log on fxp0 proto icmp all @13 block return-rst in log on fxp0 proto tcp all @14 block return-rst out log on fxp0 proto tcp all @15 block return-icmp(port-unr, port-unr) in log on fxp0 proto udp all @16 block return-icmp(port-unr, port-unr) out log on fxp0 proto udp all @17 block drop in log on fxp0 proto tcp from any to any port = pop3 @18 block drop in log on fxp0 proto tcp from any to any port = loc-srv @19 block drop in log on fxp0 proto tcp from any to any port = profile @20 block drop in log on fxp0 proto tcp from any to any port = netbios-ns @21 block drop in log on fxp0 proto tcp from any to any port = netbios-dgm @22 block drop in log on fxp0 proto tcp from any to any port = netbios-ssn @23 block drop in log on fxp0 proto tcp from any to any port = microsoft-ds @24 block drop in log on fxp0 proto udp from any to any port = pop3 @25 block drop in log on fxp0 proto udp from any to any port = loc-srv @26 block drop in log on fxp0 proto udp from any to any port = profile @27 block drop in log on fxp0 proto udp from any to any port = netbios-ns @28 block drop in log on fxp0 proto udp from any to any port = netbios-dgm @29 block drop in log on fxp0 proto udp from any to any port = netbios-ssn @30 block drop in log on fxp0 proto udp from any to any port = microsoft-ds @31 block drop out log on fxp0 proto tcp from any to any port = pop3 @32 block drop out log on fxp0 proto tcp from any to any port = loc-srv @33 block drop out log on fxp0 proto tcp from any to any port = profile @34 block drop out log on fxp0 proto tcp from any to any port = netbios-ns Just in case: # pfctl -sr -g | grep lo0 @0 pass quick on lo0 all Best regards, Anton smime.p7s Description: S/MIME Cryptographic Signature
Re: math/grace port: "libXcursor.so.1.0" not found ??
On Wed, Oct 26, 2005 at 01:16:46AM -0700, Rob wrote: > > > --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote: > > > > > > I'm running FreeBSD 5-Stable. > > > > > > I only seem to encounter this problem with the > > > math/graphical port 'grace', and the dlopen() > > > call inthere. > > > > I answered this question the last time you posted > > it. > > Yes, indeed. Thank you. You said: > "Sounds like the application is broken for >requesting it, since as you found there is >no such library on FreeBSD." > > Here "the application" refers to what? > Grace? Or dlopen()? The former. > If you mean grace, then I have a problem: > the grace mailinglist blames FreeBSD, and > here grace is blamed. Argh! It's quite obvious that FreeBSD doesn't include the library that grace is asking for, because *NO* FreeBSD libraries use the form libfoo.so.x.y (they're all libfoo.so.x). kKris pgplqKjNJRP8B.pgp Description: PGP signature
Re: math/grace port: "libXcursor.so.1.0" not found ??
--- Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote: > > > > I'm running FreeBSD 5-Stable. > > > > I only seem to encounter this problem with the > > math/graphical port 'grace', and the dlopen() > > call inthere. > > I answered this question the last time you posted > it. Yes, indeed. Thank you. You said: "Sounds like the application is broken for requesting it, since as you found there is no such library on FreeBSD." Here "the application" refers to what? Grace? Or dlopen()? If you mean grace, then I have a problem: the grace mailinglist blames FreeBSD, and here grace is blamed. Argh! I am the only FreeBSD user on the Grace mailinglist. Apparently the dlopen() call in grace works fine on Linux and others. But not with FreeBSD. Is there something fishy or tricky about the dlopen() call on FreeBSD, when compared to, for example, Linux? Grace runs fine on FreeBSD, until I use it such that it does the 'dlopen()' call. I am at a total loss here How can I further analyse this problem? Thanks, Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pf and short packets
dawnshade wrote: On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote: tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > 127.0.0.1.643: . ack 30 win 65535 0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab .)]. 0x0020: 5db7 f2f2 5010 7dce ]...P...}... 34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514 > 127.0.0.1.643: . ack 30 win 65535 0x: 4600 002c d21d 4000 0306 a5ac 7f00 0001 F..,[EMAIL PROTECTED] 0x0010: 7f00 0001 0100 0202 0283 8129 5dab .)]. 0x0020: 5db7 f2f2 5010 7dce ]...P...}... The rule for this packet is not a "log" one, but the sign (short) is what i cannot understand. Read 'man 1 tcpdump' about key "-s". You command must be like "tcpdump -s 1000 -n -e -ttt -x -i pflog0 host 127.0.0.1" Change value 1000 to appropriate. Hi, and thanks for the replay, but my question is not about how to use tcpdump (i know -s key), but what to do with pf to make this packets pass through. When my pf is up i cannot rsh to ipcad, but when it is down - everything is working just fine. I need this rsh to get my ip statistics. Best regards, Anton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" smime.p7s Description: S/MIME Cryptographic Signature
Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated
Confirmed, no more leaks. I put it 1 hour ago onto 1 production server, and today evening I'll put it to another one. Every server serves up to 2 million SMTP connections per day: load are heavy. Both servers SMP. Gleb Smirnoff wrote: GS> please confirm that the attached patch fix your problem. The patch is relative GS> to src/sys tree. -- UKR.NET Postmaster ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: math/grace port: "libXcursor.so.1.0" not found ??
On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote: > > Hi, > > I'm running FreeBSD 5-Stable. > > I only seem to encounter this problem with the > math/graphical port 'grace', and the dlopen() > call inthere. I answered this question the last time you posted it. Kris pgpQ418EGqdDv.pgp Description: PGP signature
Re: 6.0 RC1 usbd.conf (and installation comments)
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote: > most files in /etc/rc.d changed, so installing them all with > mergemaster was laborious - a note in UPDATING similar to that for > 5.x: > > "The simplest solution is an 'rm -rf /etc/rc.d/*' and then > 'mergemaster -i'." > > would have reminded me to do just that and saved about 10 minutes > of clicking 'q', then 'i' :) I did, in this case, run mergemaster > -i, but didn't think to do the above. On this note, I still can't > work out how to use the edit-merge part of mergemaster properly, > but it is certainly a pebkac issue. Just a few words on that point ... after some use of mergemaster, it seems to me that a big part of /etc have to be update blindly for most users (things in rc.d, and some other places where there's files that haven't to changed or that are system script that most users won't modify.) I hadn't time to add a possibility for mergemaster to perform blind updates of such files[1], but it seems not so complicated to do so. Does anyone else thinks that's an interesting idea ? [1] : providing a list of directories and/or files to mergemaster for which blind updates could be perform, for example ... -- Burelle Marwan, Equipe Bases de Donnees - LRI http://www.cduce.org ([EMAIL PROTECTED] | [EMAIL PROTECTED]) pgpENasNH0U92.pgp Description: PGP signature
