Re: Sporadical NFS errors with NetApp backend (solved)
--
Hello,
alas I get not response to my question, but some more googling and
testing leads to a solution.
With the following mount options all runs well:
tcp,rw,bg,dumbtimer,-r=32768,-w=32768
the most important thing is to not use any of the following
intr or soft
it seems (only idea and wild speculation), that with even the intr
mount option some IO ops are interrupted, so that I see the reported
errors below.
Perhaps the problem are a signal send to a thread???
Regards
Lars
In reply to Lars Köller who wrote:
> At the moment I have a really strange problem in our environment.
>
> - NetApp Cluster NFS file server
> - HPUX-11, Solaris-8, FreeBSD-4.11 Clients
>
> - 6 Virus/Spam scans a day, spread over 5 different FreeBSD Machines,
> two different hardware bases, 1GBit Network
>
> A problem occurs with the Sophos PMX (PureMessage Anti-Spam/Anti-Virus)
> Application. 1-3 times a day the following happens:
>
> - pmx_log:3 2005-06-23T12:26:58 [36968,milter] pmx_file():
> Can't append message info to
> '/usr/local/pmx4/var/qdir/tmp/1119522418-36968:135299072-ZN0IIE00EX1IKSAE.00-738-vscan1.hrz.uni-bielefeld.de':
> Bad file descriptor at
> /usr/local/pmx4/lib/site_perl/5.6.1/PureMessage/MessageFile.pm line 124.
>
> - /usr/local/pmx4/var is located on the NetApp Filer (NFSv3)
>
> - Line 124 referenced above looks like (close($f)):
>
> sub make {
> my $class = shift;
> my $fname = shift;
> my $minfo = @_ == 1 ? shift : do {
> require PureMessage::MessageInfo;
> PureMessage::MessageInfo->new(@_);
> };
> open(my $f, ">>", $fname) || die "Can't append to '$fname': $!\n";
> print $f _minfo_block($minfo);
> close($f) || die "Can't append message info to '$fname': $!";
> 1;
> }
>
> - BUT: The message-info is absolutely correct appended!
>
> This does not occur if I move /usr/local/pmx4/var on a local disk.
--
Dr. Lars Köller \ E-Mail : [EMAIL PROTECTED]
Leitung Systeme \ Tel: +49 521/106-4964, FAX: +49 521/106-154964
u. Serverdienste \ PGP-Key: http://www.uk.pgp.net/pgpnet/wwwkeys.html
- FreeBSD, what else? - http://www.de.freebsd.org -
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sporadical NFS errors with NetApp backend
Hallo,
I'm a FreeBSD user for years with machines in production since V2.X.
At the moment I have a really strange problem in our environment.
- NetApp Cluster NFS file server
- HPUX-11, Solaris-8, FreeBSD-4.11 Clients
- 6 Virus/Spam scans a day, spread over 5 different FreeBSD Machines,
two different hardware bases, 1GBit Network
A problem occurs with the Sophos PMX (PureMessage Anti-Spam/Anti-Virus)
Application. 1-3 times a day the following happens:
- pmx_log:3 2005-06-23T12:26:58 [36968,milter] pmx_file():
Can't append message info to
'/usr/local/pmx4/var/qdir/tmp/1119522418-36968:135299072-ZN0IIE00EX1IKSAE.00-738-vscan1.hrz.uni-bielefeld.de':
Bad file descriptor at
/usr/local/pmx4/lib/site_perl/5.6.1/PureMessage/MessageFile.pm line 124.
- /usr/local/pmx4/var is located on the NetApp Filer (NFSv3)
- Line 124 referenced above looks like (close($f)):
sub make {
my $class = shift;
my $fname = shift;
my $minfo = @_ == 1 ? shift : do {
require PureMessage::MessageInfo;
PureMessage::MessageInfo->new(@_);
};
open(my $f, ">>", $fname) || die "Can't append to '$fname': $!\n";
print $f _minfo_block($minfo);
close($f) || die "Can't append message info to '$fname': $!";
1;
}
- BUT: The message-info is absolutely correct appended!
This does not occur if I move /usr/local/pmx4/var on a local disk.
No errors in any logfile!
No problems with other Servers!
Any ideas? Is there a kernel NFS or interoperability problem with the
NetApp Filer.
How can I debug this on FreeBSD?
Best regards
Lars
--
Lars Köller \ Raum : V0-318 (Tel: 4964, FAX: 154964)
Leitung Systeme \ E-Mail : [EMAIL PROTECTED]
u. Serverdienste \ PGP-Key: http://www.uk.pgp.net/pgpnet/wwwkeys.html
-- FreeBSD, what else? http://www.de.freebsd.org -
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-rc1 Install and USB mouse problems
Hello! In reply to "Lars =?iso-8859-1?Q?K=F6ller?=" who wrote: >>Not sure here; the USB mouse on my home system (VIA KT400 chipset) works >>as expected. perhaps there are two mouseds running? > >No, nothing in that area. At the moment I think it has to do with the >usb code in the 5.2 kernel. The problem is I don't have an idea how to >further debug. > >Do you know an USB-coding-expert, who can debug this with me? >Would be nice to have a mouse even when changing to 5.2 ;-) I've further test the extra USB2+FW Combo card, and if I plug my mouse there it will run in under 4.9 and 5.2. However something in 5.2 has changed, which avoids a working usb mouse with the onboard VIA usb port. The board is a Gigabyte GA6VXDC2 (SMP). I've detached and reattached the mouse to the onboard usb bus, and see: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 port 1 addr 0 should never happen! port 2 powered Attached are the dmesg.boot file for my 4.9 and 5.2 system and the usbdevs -v output under 5.2 and 4.9. Have a look at the "shadow" device in usbdev2-49.out after deconnecting the mouse from the PCI card usb device and reconnect it to the onboard usb slot. Perhaps someone can have a look at it. Again best regards and merry christmas ;-) Lars -- Lars Köller E-Mail: [EMAIL PROTECTED] ([EMAIL PROTECTED]) FreeBSD, was sonst? http://www.de.freebsd.org Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, PS2/USB Browser Combo Mouse(0x0011), Cypress Sem(0x05fe), rev 0.10 Controller /dev/usb2: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 port 1 addr 2: low speed, power 100 mA, config 1, PS2/USB Browser Combo Mouse(0x0011), Cypress Sem(0x05fe), rev 0.10 port 2 powered Controller /dev/usb1: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, product 0x0011(0x0011), Chic Technology(0x05fe), rev 0.10 Controller /dev/usb2: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 powered Copyright (c) 1992-2003 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 4.9-RELEASE #0: Tue Oct 28 23:58:41 CET 2003 [EMAIL PROTECTED]:/opt/temp/obj/usr/src/sys/ODIE Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III (800.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 536805376 (524224K bytes) avail memory = 518049792 (505908K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0446000. Preloaded elf module "splash_pcx.ko" at 0xc044609c. Preloaded elf module "vesa.ko" at 0xc0446140. Preloaded splash_image_data "/boot/splash.pcx" at 0xc04461dc. Preloaded elf module "procfs.ko" at 0xc044622c. Preloaded elf module "vn.ko" at 0xc04462cc. Preloaded elf module "if_tun.ko" at 0xc0446368. Preloaded elf module "miibus.ko" at 0xc0446408. Preloaded elf module "if_xl.ko" at 0xc04464a8. Preloaded elf module "snd_sb16.ko" at 0xc0446548. Preloaded elf module "snd_sbc.ko" at 0xc04465e8. Preloaded elf module "snd_pcm.ko" at 0xc0446688. Preloaded elf module "usb.ko" at 0xc0446728. Preloaded elf module "ugen.ko" at 0xc04467c4. Preloaded elf module "uhid.ko" at 0xc0446860. Preloaded elf module "ukbd.ko" at 0xc04468fc. Preloaded elf module "ums.ko" at 0xc0446998. Preloaded elf module "umass.ko" at 0xc0446a34. Preloaded elf module "uscanner.ko" at 0xc0446ad4. Preloaded elf module "snp.ko" at 0xc0446b74. Preloaded elf module "firewire.ko" at 0xc0446c10. Preloaded elf module "sbp.ko" at 0xc0446cb0. VESA: v3.0, 65536k memory, flags:0x1, mode table:0xc0366282 (122) VESA: NVidia Pentium Pro MTRR support enabled acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast"
Re: 5.2-rc1 Install and USB mouse problems
In reply to Doug White who wrote: >> Hmm, I don't really understand that, cause the downloaded image burn to >> a cdrw don't boot. If I use the same cd and rerecord it with >> >> mkisofs -b /cdrom/floppies/boot.flp /cdrom > >Ah, so the controller isn't picking up non-emulated cds. If its a >separate controller you might check for a firmware update, or if its >integrated check for a system BIOS update. The systems I have with >embedded 2940s boot non-emulated discs fine. It's an separate PCI card and it has the latest Adaptec BIOS 2.20. >> I've tracked it down. The problem was induced due to mess in the >> boot loader and BIOS disk order. The smart boot loader was not loaded >> from the first BIOS disk (ad0) but from the first SCSI disk. So it >> thinks the ad disk was BIOS HD3 .. >> >> After fixing that all runs well out of the box! Sorry! > >Cool. Yes thats really fine. >> I've just trying to migrate my config and scripts from 4.9 to 5.2 so >> I'm able to fix the xperfmon3 compile problem. >> >> However, the usb mouse didn't work. Booting in 4.9 all runs well. In >> 5.2 the usbdev -v hangs about 5 seconds on the first hub. The mouse is >> recognized, but the cursor didn't move. (I've also cvsup to the latest >> sources and build my own kernel). > >Not sure here; the USB mouse on my home system (VIA KT400 chipset) works >as expected. perhaps there are two mouseds running? No, nothing in that area. At the moment I think it has to do with the usb code in the 5.2 kernel. The problem is I don't have an idea how to further debug. Do you know an USB-coding-expert, who can debug this with me? Would be nice to have a mouse even when changing to 5.2 ;-) Best regards and merry christmas Lars -- Lars Köller E-Mail: [EMAIL PROTECTED] ([EMAIL PROTECTED]) FreeBSD, was sonst? http://www.de.freebsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-rc1 Install
Hi, many thanks for the quick answer, even you are resolving the last hicks before 5.2 is released . In reply to Doug White who wrote: >> I'm trying to install a 5.2 system and have had a lot of trouble: >> >> - The disk images won't boot on my Adaptec 2940UW controller with the >>latest Firmware. >>I have to make an image by myself with mkisofs and cdrecord. After >>this all boots well. > >Odd... the Adaptec BIOS is known to have problems if you have missing or >invalid DOS slice tables. Don't run using 'dedicated' mode with Adaptecs, >at least with the first boot volume. Hmm, I don't really understand that, cause the downloaded image burn to a cdrw don't boot. If I use the same cd and rerecord it with mkisofs -b /cdrom/floppies/boot.flp /cdrom it boots! Even the FreeBSD Mall 5.X CD's don't boot, but the 4.X do. >> - My installation isn't runable, cause the kernel don't find the rootfs > >Since you have FreeBSD installed twice and you are spanning IDE and SCSI >disks, its entirely possible you're booting the wrong loader and its >getting confused, or loader itself is getting confused because of the >multiple FreeBSD installs. You should make sure that the 'rootdev' >variable in the loader is set properly before jumping into the kernel. You >can set it by dropping to the loader OK prompt and typing > >set rootdev=diskXs1a > >where X is the disk number, printed when loader starts up. > >Some BIOSes have lots of issues with booting across IDE and SCSI disks in >the same system. I've tracked it down. The problem was induced due to mess in the boot loader and BIOS disk order. The smart boot loader was not loaded from the first BIOS disk (ad0) but from the first SCSI disk. So it thinks the ad disk was BIOS HD3 .. After fixing that all runs well out of the box! Sorry! I've just trying to migrate my config and scripts from 4.9 to 5.2 so I'm able to fix the xperfmon3 compile problem. However, the usb mouse didn't work. Booting in 4.9 all runs well. In 5.2 the usbdev -v hangs about 5 seconds on the first hub. The mouse is recognized, but the cursor didn't move. (I've also cvsup to the latest sources and build my own kernel). 4.9-RELEASE: [EMAIL PROTECTED]:~/ 143130 : usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 1.00 port 1 addr 2: low speed, power 100 mA, config 1, PS2/USB Browser Combo Mouse(0x0011), Cypress Sem(0x05fe), rev 0.10 port 2 powered Controller /dev/usb1: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: self powered, config 1, OHCI root hub(0x), NEC(0x), rev 1.00 port 1 powered port 2 powered 5.2-RC: The same output, but also the USB2 device is recognized. Any ideas? (vidcontrol -m on, moused parameters, are o.k. usbd also starts the mouse .) Best regards Lars -- Lars Köller E-Mail: [EMAIL PROTECTED] ([EMAIL PROTECTED]) FreeBSD, was sonst? http://www.de.freebsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.2-rc1 Install
Hi, I'm trying to install a 5.2 system and have had a lot of trouble: - The disk images won't boot on my Adaptec 2940UW controller with the latest Firmware. I have to make an image by myself with mkisofs and cdrecord. After this all boots well. - My installation isn't runable, cause the kernel don't find the rootfs - Disk configuration: - ad0 (s1: FreeBSD-4.0) - da0 (s1: FAT32, W98) - da1 (s1: FBSD-5.2) - da2 (s1: FAT32) I install on da1 without any problems. After the reboot all the disks are found by GEOM. However the kernel only finds da0s1a da1 ad0s1a as a rootfs, da1s1a is missing. The disk numeration is the same as during the install. Cause I have no access to ufs2 I'm not able to have a look into it from the running 4.9 system. The disklabel seems to bo o.k.: [EMAIL PROTECTED]:~/ 142646 : disklabel da1s1 # /dev/da1s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD 2048 16384 28552 # (Cyl.0 - 261*) b: 1073152 6291456 swap# (Cyl. 391*- 458*) c: 177678270unused0 0 # (Cyl.0 - 1105*) d: 1048576 41943044.2BSD 2048 16384 8 # (Cyl. 261*- 326*) e: 1048576 52428804.2BSD 2048 16384 8 # (Cyl. 326*- 391*) f: 10403219 73646084.2BSD 2048 16384 28552 # (Cyl. 458*- 1105*) super block size 0 Any ideas? Best regards Lars -- Lars Köller E-Mail: [EMAIL PROTECTED] ([EMAIL PROTECTED]) FreeBSD, was sonst? http://www.de.freebsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unable to share 100MB Zip medium between ATAPI-FD and USB ZIP
Dear experts, I'm using FreeBSD-4.9 RELEASE on two different machines. One with an NEC 100MB ATAPI Zip drive and another with an 250MB USB Zip drive. The 100MB medium can't be exchanged between the two drives when it is labled and ufs formatted. The partition and label in the 250 MB USB Zip drive works well, but can only be udes as /dev/afd0a on the ATAPI drive. Partition and newfs on the ATAPI drive only works, when I cut off 32 sectors of the partition a. Otherwise I get 96904 : disklabel afd0 # /dev/afd0c: type: ESDI disk: afd0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 95 sectors/unit: 196576 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 1965760unused0 0 # (Cyl.0 - 95*) [EMAIL PROTECTED]:~/ 96905 : newfs /dev/afd0c Warning: Block size restricts cylinders per group to 97. Warning: 32 sector(s) in last cylinder unallocated /dev/afd0c: 196576 sectors in 48 cylinders of 1 tracks, 4096 sectors 96.0MB in 1 cyl groups (97 c/g, 194.00MB/g, 12288 i/g) super-block backups (for fsck -b #) at: write error: 196575 newfs: wtfs - writecombine: Input/output error There seems to be a 32 sector difference induced by the driver, or the drive? Who can help? Regards Lars -- Lars Köller E-Mail: [EMAIL PROTECTED] ([EMAIL PROTECTED]) FreeBSD, was sonst? http://www.de.freebsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
-- Hello, anything news concerning my SMP problem with the Fujitsu-Siemens RX300 system? Would be nice to have SMP running at Friday evening, when I have to go into production. Thanks and best regards Lars -- E-Mail: [EMAIL PROTECTED]\ Lars Köller [EMAIL PROTECTED] \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 --- FreeBSD, what else? http://www.freebsd.org - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
: 0xc000 -- Bus Heirarchy bus ID: 5 bus info: 0x01 parent bus ID: 0 -- Compatibility Bus Address bus ID: 0 address modifier: add predefined range: 0x -- Compatibility Bus Address bus ID: 0 address modifier: add predefined range: 0x0001 -- Compatibility Bus Address bus ID: 1 address modifier: subtract predefined range: 0x -- Compatibility Bus Address bus ID: 1 address modifier: subtract predefined range: 0x0001 -- Compatibility Bus Address bus ID: 2 address modifier: subtract predefined range: 0x -- Compatibility Bus Address bus ID: 2 address modifier: subtract predefined range: 0x0001 -- Compatibility Bus Address bus ID: 3 address modifier: subtract predefined range: 0x -- Compatibility Bus Address bus ID: 3 address modifier: subtract predefined range: 0x0001 -- Compatibility Bus Address bus ID: 4 address modifier: subtract predefined range: 0x -- Compatibility Bus Address bus ID: 4 address modifier: subtract predefined range: 0x0001 === Lars -- E-Mail: [EMAIL PROTECTED]\ Lars Köller [EMAIL PROTECTED] \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 --- FreeBSD, what else? http://www.freebsd.org - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
ra320 Wide Channel B, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs pcib4: on motherboard pci4: on pcib4 pcib5: on motherboard pci5: on pcib5 pcib6: on motherboard pci6: on pcib6 pcib7: on motherboard pci7: on pcib7 orm0: at iomem 0xc-0xc8fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <12 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 APIC_IO: Testing 8254 interrupt delivery Best Regards Lars -- E-Mail: [EMAIL PROTECTED]\ Lars Köller [EMAIL PROTECTED] \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 --- FreeBSD, what else? http://www.freebsd.org - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
Hi experts, I need urgently help or a patch for FreeBSD-4-STABLE on a Fujitsu-Siemens RX300 hardware: - The non-SMP kernel runs well - With the SMP kernel a lockup occur after the 8254 interrupt delivery is tested: ... APIC_IO: Testing 8254 interrupt delivery I've checked with hyper threading enabled/disabled. attached is the kernel configuration. Thanks and best regards Lars -- E-Mail: [EMAIL PROTECTED] \ Lars Köller [EMAIL PROTECTED] \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 --- FreeBSD, what else? http://www.freebsd.org - VSCAN.FSC-SMP Description: VSCAN.FSC-SMP ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Missing file - Help!
--
Hi
and NO. The notation is the desired one for the ports mechanism!
In reply to Kevin Golding who wrote:
> Someone, quite probably Steven Lake, once wrote:
> > Someone mentioned to me that this is supposed to come with the
> >app "gettext". But I'm not sure.
>
> Well the ports Makefile for apcupsd contains the line:
> LIB_DEPENDS=intl.4:${PORTSDIR}/devel/gettext
>
> But the pkg-plist for gettext doesn't mention intl.4, the closest is
> lib/libintl.so.4
>
> It looks like the port for apcupsd may need updating.
>
> Kevin
>
> >On Thu, 2 Jan 2003, Gregory Carvalho wrote:
> >
> >> I know you didn't ask, but you might consider using NUT (Network UPS
> >> Tools) which has extensive architecture and device support (including
> >> USB UPSes).
> >>
> >> BTW, I used:
> >>
> >> find / -name "int*4"
> >>
> >> on FreeBSD 3.2, FreeBSD 4.6, and FreeBSD 4.7 Release, but the results
> >> did not contain your indicated file.
> >>
> >> Steven Lake wrote:
> >> >
> >> > Hi all. I was trying to build and install apcupsd and during the
> >> > build I get this error: shared library "intl.4" does not exist
> >> >
> >> > Anybody know how to fix this? I've never seen this error before
> >> > and have no idea what this file is or does. Thanks for the help.
> >>
> >>
> >
> >
> >To Unsubscribe: send mail to [EMAIL PROTECTED]
> >with "unsubscribe freebsd-questions" in the body of the message
>
> --
> [EMAIL PROTECTED]
--
E-Mail: [EMAIL PROTECTED]\ Lars Köller
[EMAIL PROTECTED] \ CC University of
PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany
Key-ID: A430D499 \ Tel: +49 521 106 4964
--- FreeBSD, what else? http://www.freebsd.org -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
