Re: What's happening to my asciidoc?
On 06.09.2013 22:52, Warren Block wrote: On Fri, 6 Sep 2013, David Demelier wrote: 2013/9/6 Warren Block wbl...@wonkity.com: asciidoc \ -a data-uri \ -a icons \ -a iconsdir=/usr/local/etc/asciidoc/images/icons \ -d article \ -a stylesheet=~/docs/stylesheets/wb-html.css \ -a toc \ -a revdate=2013-09-05 \ -a year=2013 \ -a max-width=80em \ pxe.txt That stylesheet is just my changes to the default, which change the link visited color from pink to red and add rounded corners to listing blocks. Did you touch the asciidoc configuration ? For me it seems to work *only* if I use html5 backend, otherwise it produces this: http://www.demelierdavid.fr/article.html. Not that I recall, and pkg-info -g asciidoc-8.6.8_1 does not show anything. I've found the problem but can't fix it. The xhtml11.conf is the copy of wordpress.conf. I've sent a PR: ports/181869 Note that this only happen when I use pkgng + poudriere. Regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening to my asciidoc?
2013/9/6 Warren Block wbl...@wonkity.com: On Thu, 5 Sep 2013, Warren Block wrote: On Thu, 5 Sep 2013, David Demelier wrote: Hi, I've been using asciidoc for a while, I've updating it to asciidoc-8.6.8_1. But now I can't generate any correct documentation. It does not even add :toc: field. For instance the following example should generate a HTML with its popular blue theme : Test === :Author: David :toc: = Title Some data == Title 2 Some data For me, it produces a very light HTML file with no table of content and everything is black, I also notice that it does not append any CSS code. Does anyone already have this issue? It's working for me, I used it last night. Here is the command I use (generated from a Makefile), broken into separate lines: asciidoc \ -a data-uri \ -a icons \ -a iconsdir=/usr/local/etc/asciidoc/images/icons \ -d article \ -a stylesheet=~/docs/stylesheets/wb-html.css \ -a toc \ -a revdate=2013-09-05 \ -a year=2013 \ -a max-width=80em \ pxe.txt That stylesheet is just my changes to the default, which change the link visited color from pink to red and add rounded corners to listing blocks. Did you touch the asciidoc configuration ? For me it seems to work *only* if I use html5 backend, otherwise it produces this: http://www.demelierdavid.fr/article.html. Cheers, -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening to my asciidoc?
On Thu, 5 Sep 2013, Warren Block wrote: On Thu, 5 Sep 2013, David Demelier wrote: Hi, I've been using asciidoc for a while, I've updating it to asciidoc-8.6.8_1. But now I can't generate any correct documentation. It does not even add :toc: field. For instance the following example should generate a HTML with its popular blue theme : Test === :Author: David :toc: = Title Some data == Title 2 Some data For me, it produces a very light HTML file with no table of content and everything is black, I also notice that it does not append any CSS code. Does anyone already have this issue? It's working for me, I used it last night. Here is the command I use (generated from a Makefile), broken into separate lines: asciidoc \ -a data-uri \ -a icons \ -a iconsdir=/usr/local/etc/asciidoc/images/icons \ -d article \ -a stylesheet=~/docs/stylesheets/wb-html.css \ -a toc \ -a revdate=2013-09-05 \ -a year=2013 \ -a max-width=80em \ pxe.txt That stylesheet is just my changes to the default, which change the link visited color from pink to red and add rounded corners to listing blocks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening to my asciidoc?
On Thu, 5 Sep 2013, David Demelier wrote: Hi, I've been using asciidoc for a while, I've updating it to asciidoc-8.6.8_1. But now I can't generate any correct documentation. It does not even add :toc: field. For instance the following example should generate a HTML with its popular blue theme : Test === :Author: David :toc: = Title Some data == Title 2 Some data For me, it produces a very light HTML file with no table of content and everything is black, I also notice that it does not append any CSS code. Does anyone already have this issue? It's working for me, I used it last night. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening
On Tue, Jun 23, 2009 at 05:28:51PM +0200, Jack Raats wrote: Can anyone explain this: Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP What's causing this??? The wire was disconnected during that time. Possibly the hub/switch lost power, or the modem was down. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening
David Kelly writes: Can anyone explain this: Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP What's causing this??? The wire was disconnected during that time. Possibly the hub/switch lost power, or the modem was down. It also happens to some cards during boot-up. I have an Intel Pro/1000, connected to a live switch; during boot I get an UP-DOWN-UP transition. As far as I can tell, it's harmless. To the OP: does this transition affect traffic? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening
Robert Huff wrote: David Kelly writes: Can anyone explain this: Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP What's causing this??? The wire was disconnected during that time. Possibly the hub/switch lost power, or the modem was down. It also happens to some cards during boot-up. I have an Intel Pro/1000, connected to a live switch; during boot I get an UP-DOWN-UP transition. As far as I can tell, it's harmless. To the OP: does this transition affect traffic? Robert Huff depending in the switch, it could be negotiating speed/duplex. Some if configured to auto switch will do it continuously ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening
Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP look at time. it's 13 minutes down ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: What's happening
There's not NEARLY enough info in OP to answer this - I can't believe anyone is even trying. It could be many dozen different things. -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Wojciech Puchar Sent: Tuesday, June 23, 2009 2:47 PM To: Robert Huff Cc: FreeBSD-Questions@freebsd.org Subject: Re: What's happening Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP look at time. it's 13 minutes down ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's happening
Well, sorta true. We know that he lost connectivity for 13 minutes. As you said, there are many reasons why this might be so, and several were suggested. The two most likely are: 1) power loss to the switch 2) somebody disconnected the cable, then replaced it Clearly, however, it isn't port negotiation - not over 13 minutes. Unfortunately, he probably doesn't have a central syslog server that collects data from hosts and other equipment, because that's the only way to tell for sure. Things like UPS power loss/fluctuation notifications, switch bootup notifications, etc., in the syslog would provide the necessary data. Kurt On Tue, Jun 23, 2009 at 14:00, Gary Gattenggat...@waddell.com wrote: There's not NEARLY enough info in OP to answer this - I can't believe anyone is even trying. It could be many dozen different things. -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Wojciech Puchar Sent: Tuesday, June 23, 2009 2:47 PM To: Robert Huff Cc: FreeBSD-Questions@freebsd.org Subject: Re: What's happening Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP look at time. it's 13 minutes down ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: What's happening
Since we're speculating, could be the switch disabled the port due to a security event of some sort (flapping, bpdu guard/filter, etc.) and it's configured to auto-enable after n minutes. It's all speculation without more info. If this is the only info available, it's nearly worthless. -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Kurt Buff Sent: Tuesday, June 23, 2009 4:24 PM To: freebsd-questions@freebsd.org Subject: Re: What's happening Well, sorta true. We know that he lost connectivity for 13 minutes. As you said, there are many reasons why this might be so, and several were suggested. The two most likely are: 1) power loss to the switch 2) somebody disconnected the cable, then replaced it Clearly, however, it isn't port negotiation - not over 13 minutes. Unfortunately, he probably doesn't have a central syslog server that collects data from hosts and other equipment, because that's the only way to tell for sure. Things like UPS power loss/fluctuation notifications, switch bootup notifications, etc., in the syslog would provide the necessary data. Kurt On Tue, Jun 23, 2009 at 14:00, Gary Gattenggat...@waddell.com wrote: There's not NEARLY enough info in OP to answer this - I can't believe anyone is even trying. It could be many dozen different things. -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Wojciech Puchar Sent: Tuesday, June 23, 2009 2:47 PM To: Robert Huff Cc: FreeBSD-Questions@freebsd.org Subject: Re: What's happening Jun 23 17:09:09 zeus kernel: fxp0: link state changed to DOWN Jun 23 17:22:25 zeus kernel: fxp0: link state changed to UP look at time. it's 13 minutes down ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: what's happening with xorg?
On Wed, Oct 17, 2007 at 04:22:58AM +0200, Roland Smith wrote: On Tue, Oct 16, 2007 at 03:47:22PM -0700, Gary Kline wrote: I'm in the middle of a portupgrade -aP, and saw that the newest mga driver is installed. So I did another X -configure, moved the file to /etc/X11/xorg.conf and carefully tried out the new xf86-video-mga-1.9.100.. The screen is much brighter at the resolution is good, but the brightness is still very dingy compared to the vesa driver. There is nothing wrong with my CRT; on the other KVM connections (and/or) with the vesa driver at 800x600, the screen is completely bright. Is there some other ati driver yet to finish? The ati driver is for ATI chips like the Radeon. You could try playing with the gamma value of the monitor. When X is running you can use xgamma to adjust the gamma setting. You can also set this with the Gamma entry in the Monitor section of xorg.conf. Or should I ask somebbody to put back in the Radeon card? (i think that was the card i thought was going bad... ) Otherwise, I'll try the Gamma entry in my Monitor section with my G450. What value should I use? Or if it is boolen, do I try settting it to on?? thanks lots, gary PS: to you, or to any other driver wizards::: is this mga driver still being hacked-on? The screen is only dingy grey not black. (*mumble*) Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what's happening with xorg?
On Tue, Oct 16, 2007 at 11:46:27PM -0700, Gary Kline wrote: You could try playing with the gamma value of the monitor. When X is running you can use xgamma to adjust the gamma setting. You can also set this with the Gamma entry in the Monitor section of xorg.conf. Or should I ask somebbody to put back in the Radeon card? (i think that was the card i thought was going bad... ) Otherwise, I'll try the Gamma entry in my Monitor section with my G450. What value should I use? Or if it is boolen, do I try settting it to on?? The default setting for gamma is 1. Try e.g. 2. See also xorg.conf(5). Alternatively you can try to change it while X is running by typing 'xgamma -gamma 2' in a terminal. This does require that the VidModeExtension is active, i.e. the ServerFlags option DisableVidModeExtension should _not_ be set. PS: to you, or to any other driver wizards::: is this mga driver still being hacked-on? The screen is only dingy grey not black. (*mumble*) It looks like it is still in development; http://cgit.freedesktop.org/xorg/driver/xf86-video-mga/ BTW, I was assuming you have tried adjusting the brightness and contrast settings of the monitor? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpcJZmwqdKYc.pgp Description: PGP signature
Re: what's happening with xorg?
On Wed, Oct 17, 2007 at 08:18:53PM +0200, Roland Smith wrote: On Tue, Oct 16, 2007 at 11:46:27PM -0700, Gary Kline wrote: You could try playing with the gamma value of the monitor. When X is running you can use xgamma to adjust the gamma setting. You can also set this with the Gamma entry in the Monitor section of xorg.conf. Or should I ask somebbody to put back in the Radeon card? (i think that was the card i thought was going bad... ) Otherwise, I'll try the Gamma entry in my Monitor section with my G450. What value should I use? Or if it is boolen, do I try settting it to on?? The default setting for gamma is 1. Try e.g. 2. See also xorg.conf(5). I'll try your xgamma -gamma 2 suggestion, below. Thanks for the data-point. I read [[ skimmed-thru ]] xorg.conf. This is another man page that you've got to prrint out, go into a corner, and read ... very slowly :-| Alternatively you can try to change it while X is running by typing 'xgamma -gamma 2' in a terminal. This does require that the VidModeExtension is active, i.e. the ServerFlags option DisableVidModeExtension should _not_ be set. Good to know. So far, none of the flags are set. PS: to you, or to any other driver wizards::: is this mga driver still being hacked-on? The screen is only dingy grey not black. (*mumble*) It looks like it is still in development; http://cgit.freedesktop.org/xorg/driver/xf86-video-mga/ BTW, I was assuming you have tried adjusting the brightness and contrast settings of the monitor? Ja. In fact, only when everything is maxed out (brightness contrast) does the screen approach dingy grey. Otherwise, it's something like light mud ... and I'm not trying to be funny. At least the hackers are still developing this driver. I booted my DOS partition and it recognized problems and finally displayed a 1024x768 display. have a good one, gary Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what's happening with xorg?
On Wed, Oct 17, 2007 at 11:36:09AM -0700, Gary Kline wrote: The default setting for gamma is 1. Try e.g. 2. See also xorg.conf(5). I'll try your xgamma -gamma 2 suggestion, below. Thanks for the data-point. I read [[ skimmed-thru ]] xorg.conf. This is another man page that you've got to prrint out, go into a corner, and read ... very slowly :-| The good news is that the autodetection of Xorg has improved a lot. In a lot of cases you can run 7.3 without xorg.conf. Ja. In fact, only when everything is maxed out (brightness contrast) does the screen approach dingy grey. Otherwise, it's something like light mud ... and I'm not trying to be funny. You should make sure that this is not a hardware problem. Try using another monitor or another VGA cable. If you can get your hands on another graphics card (maybe built-in graphics on the mobo?) try that as well. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpq1u2GDs7di.pgp Description: PGP signature
Re: what's happening with xorg?
On Tue, Oct 16, 2007 at 03:47:22PM -0700, Gary Kline wrote: I'm in the middle of a portupgrade -aP, and saw that the newest mga driver is installed. So I did another X -configure, moved the file to /etc/X11/xorg.conf and carefully tried out the new xf86-video-mga-1.9.100.. The screen is much brighter at the resolution is good, but the brightness is still very dingy compared to the vesa driver. There is nothing wrong with my CRT; on the other KVM connections (and/or) with the vesa driver at 800x600, the screen is completely bright. Is there some other ati driver yet to finish? The ati driver is for ATI chips like the Radeon. You could try playing with the gamma value of the monitor. When X is running you can use xgamma to adjust the gamma setting. You can also set this with the Gamma entry in the Monitor section of xorg.conf. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpLwGXJn2dGM.pgp Description: PGP signature
Re: What's happening to FreeBSD 4.10 ?
Admin wrote: Radek Kozlowski wrote: On Thu, Nov 11, 2004 at 08:06:34PM +0100, Hasse wrote: And now ruby is seg faulting and core dumps when I run portsdb -uU odin# portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.2 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. done [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11933 port entries found .1000.2000.3000.4000.5000.6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) This has been asked too many times on the lists. See the original suggestion of portupgrade's author and/or check the archives: http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html -Radek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A. Sorry for that one. I'm a bit frustrated about my seg faulting Apache server :-) Thx for your pointer. The line ENV['PORTS_DBDRIVER'] = 'dbm_hash' have been added to my pkgtools.conf You might also have a point of direction to my other problem with seg faulting apache2 ? All my efforts are documented here if you are interested : http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html The problem seems to be the php4-pcre-4.3.9 extension. What I understand from my digging, is that 4.3.4 version should work. I just don't know how to get hold of it, or how to install it. Well, I could download php4 4.3.4 version and extract it from the extension dir, but then what ? How do I install it and where ? Any help or advice would be highly appreciated. /Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The above URL I was referring to, should offcourse have been : http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-November/064208.html / Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's happening to FreeBSD 4.10 ?
On Thu, Nov 11, 2004 at 08:45:01PM +0100, Admin wrote: You might also have a point of direction to my other problem with seg faulting apache2 ? All my efforts are documented here if you are interested : http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html The problem seems to be the php4-pcre-4.3.9 extension. What I understand from my digging, is that 4.3.4 version should work. I just don't know how to get hold of it, or how to install it. Well, I could download php4 4.3.4 version and extract it from the extension dir, but then what ? How do I install it and where ? Any help or advice would be highly appreciated. Nope, sorry. However, I use php4 with apache 1.3.x and have never had any problems, so if you don't need apache2 you might give apache1 a try. -Radek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's happening to FreeBSD 4.10 ?
Radek Kozlowski wrote: On Thu, Nov 11, 2004 at 08:45:01PM +0100, Admin wrote: You might also have a point of direction to my other problem with seg faulting apache2 ? All my efforts are documented here if you are interested : http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html The problem seems to be the php4-pcre-4.3.9 extension. What I understand from my digging, is that 4.3.4 version should work. I just don't know how to get hold of it, or how to install it. Well, I could download php4 4.3.4 version and extract it from the extension dir, but then what ? How do I install it and where ? Any help or advice would be highly appreciated. Nope, sorry. However, I use php4 with apache 1.3.x and have never had any problems, so if you don't need apache2 you might give apache1 a try. -Radek Okay, thx. No, I don't need Apache2, I'm just customed to using it. And this is a production server. Thought, I don't belive the problem are within the Apache server. If I disable the LoadModule php4_module libexec/apache2/libphp4.so in httpd.conf , the problem are gone. The funny thing is that I seems to be alone with this problem, due to the low response to my post :-) Haven' t been able to find any documentation since some posted patches for the php4-pcre-4.3.6 version , witch I tried to apply with no luck. I might try to just uninstall the hole php4 port, and rebuild it from source with version 4.3.4 that I downloaded from php.net. Never had this kind of problems with ported software before. / Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's happening to FreeBSD 4.10 ?
On Thu, Nov 11, 2004 at 08:06:34PM +0100, Hasse wrote: And now ruby is seg faulting and core dumps when I run portsdb -uU odin# portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.2 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. done [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11933 port entries found .1000.2000.3000.4000.5000.6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) This has been asked too many times on the lists. See the original suggestion of portupgrade's author and/or check the archives: http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html -Radek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's happening to FreeBSD 4.10 ?
Radek Kozlowski wrote: On Thu, Nov 11, 2004 at 08:06:34PM +0100, Hasse wrote: And now ruby is seg faulting and core dumps when I run portsdb -uU odin# portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.2 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. done [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11933 port entries found .1000.2000.3000.4000.5000.6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) This has been asked too many times on the lists. See the original suggestion of portupgrade's author and/or check the archives: http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html -Radek ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A. Sorry for that one. I'm a bit frustrated about my seg faulting Apache server :-) Thx for your pointer. The line ENV['PORTS_DBDRIVER'] = 'dbm_hash' have been added to my pkgtools.conf You might also have a point of direction to my other problem with seg faulting apache2 ? All my efforts are documented here if you are interested : http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/016006.html The problem seems to be the php4-pcre-4.3.9 extension. What I understand from my digging, is that 4.3.4 version should work. I just don't know how to get hold of it, or how to install it. Well, I could download php4 4.3.4 version and extract it from the extension dir, but then what ? How do I install it and where ? Any help or advice would be highly appreciated. /Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
