Hello Fred,
Fred writes:
> I ran into a problem when updating ports on 8.1-RELEASE (i386).
> ~/print/latex-cjk doesn't want to build.
>
> ===> Patching for latex-cjk-4.8.2_4
> ===> Applying FreeBSD patches for latex-cjk-4.8.2_4
> Ignoring previously applied (or
Hello,
I ran into a problem when updating ports on 8.1-RELEASE (i386).
~/print/latex-cjk doesn't want to build.
===> Patching for latex-cjk-4.8.2_4
===> Applying FreeBSD patches for latex-cjk-4.8.2_4
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--sav
On 03/04/2011 11:05, Paul Chany wrote:
> I have just installed FreeBSD release 8.2 using
> FreeBSD-8.2-RELEASE-i386-disc1.iso
> and want to install sudo.
>
> I did the following:
>
> # whereis sudo
> # cd /usr/ports/security/sudo
> # make install clean
>
> but g
Hi,
I have just installed FreeBSD release 8.2 using
FreeBSD-8.2-RELEASE-i386-disc1.iso
and want to install sudo.
I did the following:
# whereis sudo
# cd /usr/ports/security/sudo
# make install clean
but get error messages:
.. Could not find /usr/ports/Mk/bsd.port.mk
What can I do to solve
basically can
someone not like it?
Цhat are the disadvantages compared to " grep define
/usr/ports///Makefile "? Maybe the other of
thousand maintainrs something not know about it?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.o
> I expected to hear that just so happened historically. Тext question I
> ask only to satisfy my interest. What OPTIONS framework basically can
> someone not like it?
http://lists.freebsd.org/pipermail/freebsd-ports/2010-October/063914.html
--
Ei
ONS framework basically can
someone not like it?
Цhat are the disadvantages compared to " grep define
/usr/ports///Makefile "? Maybe the other of
thousand maintainrs something not know about it?
___
freebsd-questions@freebsd.org mailing list
On Sun, Mar 27, 2011 at 10:19:44PM +0400, Subbsd wrote:
> Ive wanted to ask why the option of vim port has not yet been handed
> via dialog by default. Personally, to make them work, we must define
> WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without
> it is so difficult ;)
Beca
Ive wanted to ask why the option of vim port has not yet been handed
via dialog by default. Personally, to make them work, we must define
WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without
it is so difficult ;)
___
freebsd-questions@fre
am I being unreasonable, or both, or not?
>
> This is unsupported, but you are not being unreasonable. This is a
> much wanted feature.
>
>> Yes. Ports which support parallel builds will have MAKE_JOBS_SAFE=yes set
>> in the port Makefile. It defaults to running -j with
>Is this possible or am I being unreasonable, or both, or not?
This is unsupported, but you are not being unreasonable. This is a
much wanted feature.
> Yes. Ports which support parallel builds will have MAKE_JOBS_SAFE=yes set in
> the port Makefile. It defaults to runnin
Hi--
[ ...followups sent to freebsd-ports@ list... ]
On Mar 15, 2011, at 12:20 PM, John wrote:
> I am no expert on make, so, here goes:
>
> Can -j options be used for make when building ports?
Yes. Ports which support parallel builds will have MAKE_JOBS_SAFE=yes set in
the port Make
Hello freebsd-questions,
I am no expert on make, so, here goes:
Can -j options be used for make when building ports? I have an AMD X2
6000+ so presumably I'd use -j3 if this is possible. I know from the
docs that -j is not recommended for make installkernel or installworld -
but for some
On Mon, Mar 14, 2011 at 11:30 PM, Scott Ballantyne wrote:
> I want to upgrade devel/icu. In updating tells me to use
>
> portmaster -r icu
>
> This starts to rebuild gnome2-fifth-toe which wants to rebuild straw.
>
> But straw is marked DEPRECATED and portmaster won't rebuild it. I
> pkg_delete d
I want to upgrade devel/icu. In updating tells me to use
portmaster -r icu
This starts to rebuild gnome2-fifth-toe which wants to rebuild straw.
But straw is marked DEPRECATED and portmaster won't rebuild it. I
pkg_delete doesn't want to delete it because gnome2-fifth-toe depends
on it.
I neve
;
> >
> > /usr/local/share/awesome/icons/awesome16.png exists, is readable and can
> > be displayed fine with display(1).
> >
> >
> > I did csup the ports tree and recompiled both awesome and imlib2, but
> > did not succeed.
> >
> >
> >
ror, that's really bad
> /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare number
> with nil
>
>
>
> /usr/local/share/awesome/icons/awesome16.png exists, is readable and can
> be displayed fine with display(1).
>
>
> I did csup the ports tre
ocal/share/awesome/icons/awesome16.png exists, is readable and can
be displayed fine with display(1).
I did csup the ports tree and recompiled both awesome and imlib2, but
did not succeed.
The entire output of startx is:
X.Org X Server 1.7.5
Release Date: 2010-02-16
X Protocol Version 11, Revisi
gt;>
>> I'm especially interested in trying FreeBSD/sparc64 port, but I'd also like
>> to
>> test the FreeBSD/powerpc and the FreeBSD/arm ports on an emulator, before
>> seeking real hardware.
>
> QEMU claims PowerPC and ARM emulation support, but I don&#
On Fri, Jan 28, 2011 at 7:43 PM, Robert Bonomi wrote:
>> From owner-freebsd-questi...@freebsd.org Fri Jan 28 11:37:00 2011
>> Date: Fri, 28 Jan 2011 18:27:35 +0100
>> From: "C. P. Ghost"
>> To: FreeBSD Mailing List
>> Subject: Emulators to test
o like to
> test the FreeBSD/powerpc and the FreeBSD/arm ports on an emulator, before
> seeking real hardware.
QEMU claims PowerPC and ARM emulation support, but I don't know if
it's good enough to run FreeBSD. PearPC is another PowerPC emulator,
but it was mainly targeted at runnin
> From owner-freebsd-questi...@freebsd.org Fri Jan 28 11:37:00 2011
> Date: Fri, 28 Jan 2011 18:27:35 +0100
> From: "C. P. Ghost"
> To: FreeBSD Mailing List
> Subject: Emulators to test non-x86 FreeBSD ports?
>
> Hello list,
>
> are there any emulato
Hello list,
are there any emulators out there that can run the non-x86 versions of FreeBSD
on a FreeBSD/i386 or FreeBSD/amd64 host?
I'm especially interested in trying FreeBSD/sparc64 port, but I'd also like to
test the FreeBSD/powerpc and the FreeBSD/arm ports on an emulator, befo
On 07/01/2011 12:43, Paul Halliday wrote:
> I am trying to build apache22 on a fresh 8.1 box from ports. It is
> dying right about here:
>
> mod_authnz_ldap.c:41:2: error: #error mod_authnz_ldap requires
> APR-util to have LDAP support built in. To fix add --with-ldap to
> ./co
I am trying to build apache22 on a fresh 8.1 box from ports. It is
dying right about here:
mod_authnz_ldap.c:41:2: error: #error mod_authnz_ldap requires
APR-util to have LDAP support built in. To fix add --with-ldap to
./configure.
Help! :)
--
Paul Halliday
http://www.pintumbler.org
> Check so you not have "perl-threaded". If you have you must type
> "portupgrade -fr perl-treaded". Othervise it just do nothing.
wow that was easy. this was the problem and it's now rebuilding everything.
thanks to everyone for their advice.
jamie
_
been set correctly. Susbsequent ports i've
installed that require perl have been built against 5.12.
jamie
Hi
Check so you not have "perl-threaded". If you have you must type
"portupgrade -fr perl-treaded". Othervise i
> Do you have PERL_VERSION= set correctly in /etc/make.conf?
This was set automatically when i first installed perl5.12. This line was later
over-written when perl5.10 was installed. Since i used portupgrade to change
back to perl5.12 this line has been set correctly. Susbsequent ports i
alled X with a window manager and
> a few other things. Somehow - not sure when and why - one of the ports
> installed perl 5.10 as a dependancy setting itself as the default perl
> installation for the system so i ended with a mix of ports build against
> different perl versions.
>
sure when and why - one of the ports installed
perl 5.10 as a dependancy setting itself as the default perl installation for
the system so i ended with a mix of ports build against different perl
versions.
I've mostly fixed this by doing a:
`env DISABLE_CONFLICTS=1 portupgra
Quoth Dan Langille on Friday, 31 December 2010:
> >Bingo! Thanks, that's exactly what I needed. Although it took a while
> >to figure out how to do it. Suggestion for Freshports: add an "add to
> >watch list" button on the page for each port.
>
> This has been in place for some time. From
>
Bingo! Thanks, that's exactly what I needed. Although it took a while
to figure out how to do it. Suggestion for Freshports: add an "add to
watch list" button on the page for each port.
This has been in place for some time. From
http://www.freshports.org/faq.php :
http://www.freshports.o
On 2010-12-30 18:16, Erik Trulsson wrote:
On Thu, Dec 30, 2010 at 08:19:00AM -0800, Chip Camden wrote:
Hello fellow BSDophiles,
The chromium port is trying my patience. I'm not using it now, because of
its unpatched vulnerabilities. Buit I'm keeping it installed, so I'll be
notified by port
Quoth Matthew Seaman on Thursday, 30 December 2010:
> On 30/12/2010 18:51, Chip Camden wrote:
> > The regular freshports newsletter includes new ports and some version
> > updates, but not all. I don't see a way to subscribe to all updates
> > for chromium (e.g.). Bu
On 30/12/2010 18:51, Chip Camden wrote:
> The regular freshports newsletter includes new ports and some version
> updates, but not all. I don't see a way to subscribe to all updates
> for chromium (e.g.). But perhaps I'm just missing the appropriate link.
>
If you make
that purpose.
> (I have never used it myself, but it looks like it should do the
> trick.)
>
>
>
>
> --
>
> Erik Trulsson
> ertr1...@student.uu.se
The regular freshports newsletter includes new ports and some version
updates, but not all. I don't see a wa
On Thu, Dec 30, 2010 at 08:19:00AM -0800, Chip Camden wrote:
> Hello fellow BSDophiles,
>
> The chromium port is trying my patience. I'm not using it now, because of
> its unpatched vulnerabilities. Buit I'm keeping it installed, so I'll be
> notified by portversion when an update comes through.
Hello fellow BSDophiles,
The chromium port is trying my patience. I'm not using it now, because of
its unpatched vulnerabilities. Buit I'm keeping it installed, so I'll be
notified by portversion when an update comes through. Is there a more
excellent way to receive the same sort of notificatio
> Just wondering about the interaction of pkg_info (no args) and having a
> ports directory.
>
> Without it it's blazing fast, with it it is just slow and sometimes just
> breaks during the listing.
>
> There is nothing in the man page about it reading the ports directory
On Sun, Dec 26, 2010 at 10:42 AM, Chris Telting
wrote:
> Just wondering about the interaction of pkg_info (no args) and having a
> ports directory.
>
> Without it it's blazing fast, with it it is just slow and sometimes just
> breaks during the listing.
>
> There is not
Just wondering about the interaction of pkg_info (no args) and having a
ports directory.
Without it it's blazing fast, with it it is just slow and sometimes just
breaks during the listing.
There is nothing in the man page about it reading the ports directory or
why it would want or ne
On Tuesday 14 December 2010 15:03:11 Mike Sabroff wrote:
>Is this the right place to post this question?
> Original Message
>
> Subject: Re: /usr/ports/net/pptpclient
> Date: Tue, 14 Dec 2010 09:41:39 -0800
> From:
Is this the right place to post this question?
Original Message
Subject: Re: /usr/ports/net/pptpclient
Date: Tue, 14 Dec 2010 09:41:39 -0800
From: Nicklas Johnson [1]
To: [2]msabr...@sbcglobal.net
CC: [3]freebsd-j
ation? Should all depending
> packages be also automatically bumped? Or portupghrade should detect
> the change and automatically upgrade dependent ports?
There's no way to do it fully automatically, but porters try to do this
by hand, by incrementing PORTREVISION for the dependent ports
behavior in such situation? Should all depending
> packages be also automatically bumped? Or portupghrade should detect the
> change and automatically upgrade dependent ports?
portupgrade -rfx atkmm atkmm should take care of the issue, although
portupgrade -rf atkmm is probably ok too, unles
e also automatically bumped? Or portupghrade should detect the
change and automatically upgrade dependent ports?
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail t
/include/X11, and none of the files listed above
>> (IntrinsicP.h, StringDefs.h, etc.) are there.
>>
>> cd'ed to /usr/ports/x11/libX11, did a 'make deinstall', 'make clean',
>> 'make install' - same results.
>>
>> Any other thou
should (re)install libX11 (I thinks that's where
> > the header files above are found).
> >
> > -Brandon
>
> Thanks for the help, Brandon.
>
> Checked /usr/local/include/X11, and none of the files listed above
> (IntrinsicP.h, StringDefs.h, etc.) are there.
On Wed, Dec 1, 2010 at 10:01, Brandon Gooch wrote:
> On Wed, Dec 1, 2010 at 11:09 AM, Kurt Buff wrote:
>> Working on 7.1 Release. Ports tree up to date, and a portupgrade -a
>> done yesterday was successful.
>>
>> I did the following:
>>
>> # cd /usr/po
On Wed, Dec 1, 2010 at 11:09 AM, Kurt Buff wrote:
> Working on 7.1 Release. Ports tree up to date, and a portupgrade -a
> done yesterday was successful.
>
> I did the following:
>
> # cd /usr/ports/net-mgmt/netdisco
> # make install
>
> It bombs out with the below err
Working on 7.1 Release. Ports tree up to date, and a portupgrade -a
done yesterday was successful.
I did the following:
# cd /usr/ports/net-mgmt/netdisco
# make install
It bombs out with the below errors - I think it's an error in libXaw,
but can't quite be sure. Any thoug
Hello all,
Anonymous wrote:
Alexander Best writes:
does anybody if there's an alternative for libm in the ports dir? i need it,
because the newest snapshots of mplayer require log2() and log2f(), which the
base libm doesn't support.
for mplayer I'd suggest using code from x2
Alexander Best writes:
> hi there,
>
> does anybody if there's an alternative for libm in the ports dir? i need it,
> because the newest snapshots of mplayer require log2() and log2f(), which the
> base libm doesn't support.
for mplayer I'd suggest using code from
t; > > > does anybody if there's an alternative for libm in the ports dir? i
> > need
> > > > it,
> > > > because the newest snapshots of mplayer require log2() and log2f(),
> > which
> > > > the
> > > > base libm doesn't
On Tue, Nov 23, 2010 at 4:15 PM, Alexander Best wrote:
> On Tue Nov 23 10, Chris Brennan wrote:
> > On Tue, Nov 23, 2010 at 4:00 PM, Alexander Best
> wrote:
> >
> > > hi there,
> > >
> > > does anybody if there's an alternative for libm in t
On Tue Nov 23 10, Chris Brennan wrote:
> On Tue, Nov 23, 2010 at 4:00 PM, Alexander Best wrote:
>
> > hi there,
> >
> > does anybody if there's an alternative for libm in the ports dir? i need
> > it,
> > because the newest snapshots of mplayer require l
On Tue, Nov 23, 2010 at 4:00 PM, Alexander Best wrote:
> hi there,
>
> does anybody if there's an alternative for libm in the ports dir? i need
> it,
> because the newest snapshots of mplayer require log2() and log2f(), which
> the
> base libm doesn't support.
>
hi there,
does anybody if there's an alternative for libm in the ports dir? i need it,
because the newest snapshots of mplayer require log2() and log2f(), which the
base libm doesn't support.
cheers.
alex
--
a13x
___
freebsd-questions@f
On 11/15/2010 9:26 AM, t...@diogunix.com wrote:
> surprisingly, the port for /usr/ports/net-im/ejabberd too tries to build a
> bunch of software usually not associated with ejabberd (such as a lot of
> Java, X11, OpenMotif, GTK and don't know what else).
>
> After hours, t
Hi ALL,
surprisingly, the port for /usr/ports/net-im/ejabberd too tries to build a
bunch of software usually not associated with ejabberd (such as a lot of
Java, X11, OpenMotif, GTK and don't know what else).
After hours, the build of ejabberd then failed with:
/local/include -rpath
Hello everybody,
just tried to build /usr/ports/mail/mutt but surprisingly got stuck with an
Error 1 though the ports collectionis updated and well maintained:
m_err -lcrypto -lasn1 -lroken -lcrypt -lssl -lcrypto -lintl -liconv -liconv
muttlib.o(.text+0x12f2): In function `mutt_mktemp
ed;
1) Use one box or jail as the build box. Only this box/jail needs a ports
tree. The others don't need /usr/ports, nor /var/db/ports or /var/db/pkg.
2a) In case of real boxes, rsync /usr/local from the build box to the other
boxes. Then re-start updated ports.
2b) In case of jail
Hi,
I have multiple jails using ezjails, approx 20.
I'm currently doing
portsnap fetch update
ezjail-admin update -P
then doing a portmaster -Bad on each jail, but its pretty time
consuming, esp when you have to peridically come back and check if its
done and do the next one.
I've tried buildin
index
samba34-libsmbclient-3.4.8 < needs updating (port has 3.4.9)
pkg_version -v is telling me samba is up-to-date with index
samba34-libsmbclient-3.4.8 needs updating..
ok. step 2, check /usr/ports/UPDATING
hbca# grep samba-3.0.37 /usr/ports/UPDATING
Grepping for specific things
< needs updating (port has 3.4.9)
pkg_version -v is telling me samba is up-to-date with index
samba34-libsmbclient-3.4.8 needs updating..
ok. step 2, check /usr/ports/UPDATING
hbca# grep samba-3.0.37 /usr/ports/UPDATING
hbca# grep -i samba-3.0.37 /usr/ports/UPDATING
hbca# grep -i samba34-lib /
On Fri, 22 Oct 2010, Justin Victoria wrote:
Step 1:
pkg_version -v:
Ok done.. bunch of stuff needs updating:
...
Step 2:
Update Ports collection: Ports collection updated everynite via cron job and
cvsup. Done...
Check /usr/ports/UPDATING..
This seems very time consuming considering i
At 10:41 AM 10/22/2010, Justin Victoria wrote:
hbca# pkgdb -F
---> Checking the package registry database
Stale origin: 'net/samba3': perhaps moved or obsoleted.
-> The port 'net/samba3' was removed on 2010-10-18 because:
"Has expired: Unsupported by the upstream. Please, consider
to up
Hi,
I have a pretty simple question regarding upgrading ports.. I am
following the handbook Section 4.5.4..
Step 1:
pkg_version -v:
Ok done.. bunch of stuff needs updating:
Ex:
hbca# pkg_version -v | grep -v "up-to-date with port"
ImageMagick-6.6.3.10< n
Is there any particular reason there are two copies of the PostgreSQL
library for the Ruby programming language in FreeBSD ports? Do the
ruby-pg and rubygem-pg ports differ in some meaningful way? The
pkg-descr files for these ports do not give any really substantial clues
to what differences
On Wed, Oct 06, 2010 at 10:18:54PM +0100, Matthew Seaman wrote:
[stuff]
Thanks! That gives me a lot to look into. I appreciate the information.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
pgpnxxRo3nzZg.pgp
Description: PGP signature
On 06/10/2010 19:06:01, Chad Perrin wrote:
> Is there some way to set up a third-party online source for ports and/or
> packages that allows users to do the same kinds of things they can do
> with the official ports system? I mean, for instance, using portversion
> to check whether t
Is there some way to set up a third-party online source for ports and/or
packages that allows users to do the same kinds of things they can do
with the official ports system? I mean, for instance, using portversion
to check whether there are new versions available (or an equivalent
operation) and
Hello all!
I found one problem using portupgrade on a number of servers, that has
NFS mounter /usr/ports from one server.
On one server portupgrade sometimes want to rebuild
/usr/ports/INDEX-7.db. While it rebuilds, another portupgrade running
on second server suddenly wants to rebuild INDEX-7
On Thu, 30 Sep 2010, Ian Smith wrote:
> countries are long gone. For some scientific (and policy) rationale of
> the increasingly fragmented nature of new allocations down to /22 (ie 64
> IP addresses) have a look at http://www.potaroo.net/tools/ipv4/
Oops; a /22 allocation is of course 4 t
umed we were in China .. see the problem?
But ignoring geopolitics or xenophobia and concentrating on technics ..
> $cmd set 1 deny log all from table\(1\) to any in via $pif
>
> The above is the first entry in my "rules" file. I know that IPFW is
> working since I ha
The above is the first entry in my "rules" file. I know that IPFW is
> working since I have blocked other ports for other services and it has
> worked correctly.
>
> The problem is that these IPs are not being blocked. I continue to see
> them listed in the httpd-error.log. I h
o a table for easier handling.
ipfw -q table 1 add 60.0.0.0/8
ipfw -q table 1 add 61.0.0.0/8
$cmd set 1 deny log all from table\(1\) to any in via $pif
The above is the first entry in my "rules" file. I know that IPFW is
working since I have blocked other ports for other services and it has
wor
On 25/09/2010 01:10:57, Devin Teske wrote:
> HINT: If you created the package from the ports tree, you can say "make
> describe" in the package's top-level port directory
> (e.g. /usr/ports/pkg_origin/some_pkg). This will produce a line that can
> be added to
On Fri, 2010-09-24 at 10:54 -0400, Rick Miller wrote:
> I've created the package and copied it to the networked media. How do
> I edit the INDEX file so that it knows how to get the file?
HINT: If you created the package from the ports tree, you can say "make
describe"
Rick Miller writes:
> On Tue, Sep 21, 2010 at 3:55 PM, Adam Vande More
> wrote:
>> On Tue, Sep 21, 2010 at 11:41 AM, wrote:
>>>
>>> Is it possible to take a port, make a package of it and put it in the
>>> packages directory of my own media?
>>
>> Sure it's easy. When build a port you can is
o
I edit the INDEX file so that it knows how to get the file?
I did figure out one way to get this to work. I copied the entry for the
port from the ports index file into the packages index file and it worked.
Whether or not it's an appropriate way, I am unsure.
__
On Tue, Sep 21, 2010 at 3:55 PM, Adam Vande More wrote:
> On Tue, Sep 21, 2010 at 11:41 AM, wrote:
>>
>> Is it possible to take a port, make a package of it and put it in the
>> packages directory of my own media?
>
> Sure it's easy. When build a port you can issue a make package command, or
>
r, it is available through the
ports collection.
You'll probably want to do something like this:
http://bsdbased.com/2010/03/23/freebsd-binary-package-repository-howto
FWIW, that's not the end all, be all to setting up your own package
repository just a reasonably simple method.
compat6x-amd64 and I'd like to have this done during install. Unfortunately,
> it does not appear that this package exists in the FreeBSD media from which
> the install occurs. However, it is available through the ports collection.
>
You'll probably want to do something like
stall.
Unfortunately, it does not appear that this package exists in the FreeBSD
media from which the install occurs. However, it is available through the
ports collection.
What is the relationship between the packages directory on the media and
the ports collection? Is there a process that ident
post a link. And if the
> maintainer is too busy with other work to do that, then, as I said,
> don't reply and let someone else explain it.
Be not too easily annoyed, to invoke the old Fidonet adage :) I've been
subscribed to questions for over 12 years, and most of these discuss
Carl Johnson writes:
> I am running rkhunter and it keeps reporting a port inconsistency
> between sockstat and netstat -a. Netstat shows an extra 5 ports open,
> but netstat doesn't show what is holding ports open, so I don't know
> what they are. Does anybody know ho
p using that.
Yes, but you'ld need several different php5-apache ports to account for
the different versions of apache available: 1.3, 2.0, 2.2 at least -- or
rather, the corresponding versions of devel/apr. apr itself can depend
optionally on mysql, postgresql, openldap, etc. etc. -- each combi
On Mon, Sep 20, 2010 at 08:00, wrote:
> I think that response was not all that unreasonable.
I'm not sure if you are referring to me or ale here.
> 3) I think (proof left to the reader) there is an apache/php package.
There's not. There's no way to run pkg_add -r and get the
apache module (
uming that 'because it was always *this* way for years' does not
mean things won't ever change. Many of these changes are logged in UPDATING.
I have been updating Apache and PHP with portupgrade for years. I also
recognize that a change in port build options may render the saved op
the subset of the 9.7 hits
that relate to my server[s].
2) apache builds w/o php, and should php4, php5, or php6 be included by
default? The base apache httpd.conf file requires several statement to
support php, they should not have to be removed if php is not installed.
On Mon, Sep 20, 2010 at 00:45, Alex Dupre wrote:
> This "issue" has been discussed too many times. The answer is simply
> "no", but you can search the archives for the actual reason. You have to
> comile the module for your specific apache installation.
>
> --
> Alex Dupre
>
If you can't be bothe
On Mon, 20 Sep 2010, Alex Dupre wrote:
> Rob Farmer ha scritto:
> > Adding a slave port would probably be a good solution and shouldn't be
> > too difficult.
>
> This "issue" has been discussed too many times. The answer is simply
> "no", but you can search the archives for the actual reason
Rob Farmer ha scritto:
> Adding a slave port would probably be a good solution and shouldn't be
> too difficult.
This "issue" has been discussed too many times. The answer is simply
"no", but you can search the archives for the actual reason. You have to
comile the module for your specific apache
h Apache, and mod_php5/libphp5.so is strictly for Apache.
>
> No, not everyone installs PHP to use with Apache, but I guess that maybe
> half do. This comes up many times in the last 5 or so years since you
> could last install the module from a package rather than only the port.
>
> I
but its processes are accounted for by both sockstat
> and netstat.
I decided to check out your idea anyways today, and it appears you were
right. I disabled and stopped all NFS and rpc processes and those extra
ports disappeared from the netstat listing. None of those ports are
listed as relate
talls PHP to use with Apache, but I guess that maybe
half do. This comes up many times in the last 5 or so years since you
could last install the module from a package rather than only the port.
It's also one of those ports that takes a good while to build on slower
hardware (which of co
Anonymous writes:
> Chuck Swiger writes:
>
>> Hi--
>>
>> On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote:
>>> The following are the ports if anybody has any ideas, but I would also like
>>> to know how to trace them down
Chuck Swiger writes:
> Hi--
>
> On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote:
>> The following are the ports if anybody has any ideas, but I would also like
>> to know how to trace them down myself:
>>
>> tcp4 0 0 *.876 *.*
Chuck Swiger writes:
> Hi--
>
> On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote:
>> The following are the ports if anybody has any ideas, but I would also like
>> to know how to trace them down myself:
>>
>> tcp4 0 0 *.876 *.*
701 - 800 of 6569 matches
Mail list logo
