-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olivier Kaloudoff schrieb:
| I would suggest that you create the corresponding sudo entry in
/etc/sudoers and use /usr/bin/sudo .
The command dont need no special privileges. It outputs a shell sniptlet
to set ENV-vars for the openpkg instance.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I'm using
~eval `openpkg rc --eval all env`
to setup the paths for a openpkg instance in the system login script.
This works fine except that the directory which is created under /tmp
could not be deleteted since the owner of the dir is t
Hi!
I have upgraded a OpenPKG Instance from 2.5 to Current and now I see in
my tripwire reports that the file /etc/openpkg/uuid will be
touched every hour, even when the contents hasn'd changed. I could
ignore this file in the tripwire config, but on the other side I ask me
why thy file is touched
Steffen Weinreich schrieb:
> Hi!
>
> recently I setup a box with OpenSolaris to experiment with some of the
> new upcoming stuff in Solaris and I am currently building openpkg on
> this box. Something in the stdio handling has changed on OpenSolaris and
> I had to patch the min
Hi!
recently I setup a box with OpenSolaris to experiment with some of the
new upcoming stuff in Solaris and I am currently building openpkg on
this box. Something in the stdio handling has changed on OpenSolaris and
I had to patch the miniperl build of the openpkg package and the perl
package to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> On Mon, Oct 30, 2006, Steffen Weinreich wrote:
>
>> I am a little bit puzzled. As far as I understood the change from End
>> August sudo should not be longer neccecary for the most tasks to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I am a little bit puzzled. As far as I understood the change from End
August sudo should not be longer neccecary for the most tasks to
maintain a openpkg instance. In the Progress of upgrading a instance
from 2.5 to 2_STABLE I found the following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> AFAIK some people have hacked together a dummy dpkg package which
> provides those symlinks for Debian/Ubuntu and this way is 100% in sync
> with the Debian/Ubuntu package management.
What we are using is a empty dummy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great, now I have managed to use my 3 main addresses in the replies to
this topic. If I try a little harder I find some more addresses to use
;-) *gg*
cheerio
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> 1. SSLSessionCache shmht:[...filename...](512000)
> 2. SSLSessionCache dbm:[...filename...]
> 3. SSLSessionCache none
>
> If the problem goes away already with (1) the SHMCB code is the problem.
> If the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> If it also fails with GCC 4.1.1 the chance was a bit reduced that it
> is a compiler bug. Although it still looks like a compiler bug. But
> BTW, isn't this problem exactly the same Mr. Peter Zimmer already
> reported tw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> In case it is an Apache and/or mod_ssl and/or OpenSSL bug you should
> retry with the latest versions from CURRENT. There we have newer
> versions of all three components and they all three contains lots of
> bugfixes. [
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
We have recently updated a bunch of maschines from sparc64-solaris9 to
sparc64-solaris10 and went into a problem with apache bailing out with
"signal Bus Error (10)" handling ssl requests with mod_ssl.
As far as I tracked the problem it is reprod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I seem to have a small problem to checkin the new interceptty package:
the "opd release" has not picked up the interceptty.patch file and
checked the package in without it. A second run does also not pickup
the patch and leads to an permission den
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf S. Engelschall schrieb:
> On Tue, Mar 21, 2006, Steffen Weinreich wrote:
>
>> Added option for a build with shared libs
>> [...]
>>%option with_fsl yes
>>%option with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I was trying to get the HP Management Agent to run under Linux with
OpenPkg but struggle with the static compiled snmpd. I have done the
following patch a while ago for our local repository and would like to
commit it in official cvs. Any objecti
Ralf S. Engelschall schrieb:
> On Thu, Jan 26, 2006, Steffen Weinreich wrote:
>
>
>> I have just tried to build ethereal from current on a plain old
>> Sparc64-Sol9 box, but I failed since the build process doesn't find a
>> working python and the bash equiv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I have just tried to build ethereal from current on a plain old
Sparc64-Sol9 box, but I failed since the build process doesn't find a
working python and the bash equivalence seems to be broken at the moment.
Therefore I like to check in to follo
Hi!
I would like to commit the folling change to the cvs:
Added $mimedefang_flags to give the administrator a opportunitiy to
pass flags to the mimefang process
cvs diff: Diffing src/mimedefang
Index: src/mimedefang/mimedefang.spec
===
Hi!
Today one of my colleagues stumbled over a full disk due to a really
large ssl.log. I admit that the loglevel was increased from warn to
debug, but OTOH shouldn´t the rc.apache keep track of all log?
cheerio
Steve
__
The
Ralf S. Engelschall wrote:
Thanks ralf, that version build without problems under Deb31 Linux2.4.
Is this a candidate for a MFC?
Just "builds" or even "runs"? If it also _RUNS_ I'll MFC it, yes.
More precisely the version builds and runs for what i have tested. This
is more or less on
Ralf S. Engelschall wrote:
On Fri, Nov 11, 2005, Ralf S. Engelschall wrote:
So, my suggestion is: try to apply the following hunk from db.patch
to the "mysql" local copy of Berkeley-DB (in subdir bdb/):
Index: os/os_open.c
--- os/os_open.c.orig 2004-09-28 18:46:57 +0200
+++ os/os_open.c
Hi!
I´m fighting with mysql on debian 3.1 for some days now. What I have
found is the following:
- A build on a fresh installation of Debian 3.1 and OPenPKG 2.5
produces a mysqld with bails out with a Sig11 directly after
start.
- The build on rm2 (our Debian3.1 buidl box) works without
Hi!
We have recently replaced one of our Sol8 Server with a Debian3.1 AMD64
System and I try to build all needed OpenPkg packages for the system. The
current bootstrap works fine so far but building gcc breaks with
configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. I
have
Hi there!
I have just uploaded a ntop.spec to the upload area. I hope it meet your
requirements :-)
cheerio
Steve
__
The OpenPKG Projectwww.openpkg.org
Developer Communication List
25 matches
Mail list logo