Patch for nagios-plugins

2010-04-20 Thread Olivier Fournier

Hi All,

on my system (Solaris 10 x86 64-bit), version 1.4.14 of the 
nagios-plugins did not build successfully. It stopped with the following 
library compatibility error:



/openpkg/bin/cc -m64 -O2 -pipe -m64 -o pst3 pst3-pst3.o  -L/openpkg/lib 
-L/openpkg/RPM/TMP/nagios-3.2.1/nagios-plugins-1.4.14/plugins-root 
-lpthread -ldl -lssl -lcrypto
/openpkg/bin/ld: skipping incompatible /openpkg/lib/libssl.a when 
searching for -lssl
/openpkg/bin/ld: skipping incompatible 
/openpkg/lib/gcc/i386-pc-solaris2.10/4.2.4/../../../libssl.a when 
searching for -lssl

/openpkg/bin/ld: cannot find -lssl
collect2: ld returned 1 exit status
make[2]: *** [pst3] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
+ exit 2


I don't know if this issue is related to OpenSSL 1.0, but I don't think 
so. Switching to 32-bit mode for this particular pst3 file (used by the 
check_procs command) solved the problem, so I made the following 
adjustments in the patch files of the Nagios package:
- nagios.patch was modified to only handle the basic Nagios package. 
That means, the modifications concerning nagios-plugins were moved to 
the nagios-plugins.patch file
- nagios-plugins.patch was created from scratch. The file contains the 
modifications related to the nagios-plugins that were already part of 
the package + my modifications to make it build under Solaris 10


Then, the nagios.spec file was modified for the following reasons:
- It had to take in account the new patch (nagios-plugins.patch)
- Because the package is created as user openpkg, the checks that 
require root permissions are not installed per default. This can be 
forced using the make install-root target
- The ownership of these root plugins has to be root:root, otherwise 
they will refuse to run, so these settings have to be adjusted at the 
end of the package creation


I hope these modifications are useful for some of you.

Best Regards,
Olivier


Index: base/logging.c
--- base/logging.c.orig	2007-10-29 00:21:29 +0100
+++ base/logging.c	2008-05-28 08:27:03 +0200
@@ -204,6 +204,7 @@
 
 /* write something to the syslog facility */
 int write_to_syslog(char *buffer, unsigned long data_type){
+static int logopen = 0;
 
 	if(buffer==NULL)
 		return ERROR;
@@ -220,6 +221,12 @@
 	if(!(data_type  syslog_options))
 		return OK;
 
+	/* OSSP fsl identification */
+	if (!logopen) {
+		openlog(nagios, LOG_NDELAY, LOG_USER);
+		logopen = 1;
+	}
+
 	/* write the buffer to the syslog facility */
 	syslog(LOG_USER|LOG_INFO,%s,buffer);
 
Index: base/utils.c
--- base/utils.c.orig	2008-03-10 21:58:33 +0100
+++ base/utils.c	2008-05-28 08:27:03 +0200
@@ -499,7 +499,7 @@
 		/* report an error if we couldn't run the command */
 		if(fp==NULL){
 
-			strncpy(buffer,(Error: Could not execute command)\n,sizeof(buffer)-1);
+			snprintf(buffer,sizeof(buffer)-1,(Error: Could not execute command \%s\), cmd);
 			buffer[sizeof(buffer)-1]='\x0';
 
 			/* write the error back to the parent process */
##
##  nagios.spec -- OpenPKG RPM Package Specification
##  Copyright (c) 2000-2010 OpenPKG Foundation e.V. http://openpkg.net/
##
##  Permission to use, copy, modify, and distribute this software for
##  any purpose with or without fee is hereby granted, provided that
##  the above copyright notice and this permission notice appear in all
##  copies.
##
##  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
##  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
##  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
##  IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR
##  CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
##  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
##  LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
##  USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
##  ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
##  OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
##  OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
##  SUCH DAMAGE.
##

#   package versions
%define   V_nagios   3.2.1
%define   V_nagios_plugins   1.4.14
%define   V_perl_nagios_plugin   0.34
%define   V_perl_nagios_object   0.20
%define   V_perl_nagios_cmd  0.05

#   package information
Name: nagios
Summary:  System and Network Monitoring
URL:  http://www.nagios.org/
Vendor:   Ethan Galstad et al.
Packager: OpenPKG Foundation e.V.
Distribution: OpenPKG Community
Class:PLUS
Group:Monitoring
License:  GPL
Version:  %{V_nagios}
Release:  20100416

#   package options
%option   with_perl   yes
%option   with_fslyes

#   list of sources
Source0:  

OpenPKG-4: problem compiling nail on Solaris 10 x86

2010-04-16 Thread Olivier Fournier

Hi All,

I have a problem compiling nail under Solaris 10 x86 (see log below). Is 
it related to the new version of OpenSSL ?


How can I fix this issue?

Thanks a lot in advance.

Regards,
Olivier


/openpkg/bin/cc -O2 -pipe -I/openpkg/include 
-DMAILRC='/openpkg/etc/nail/nail.rc' -DMAILSPOOL='/var/mail' 
-DSENDMAIL='/openpkg/sbin/sendmail' -c openssl.c
openssl.c:108: error: expected declaration specifiers or '...' before 
'STACK'

openssl.c: In function 'ssl_select_method':
openssl.c:215: warning: assignment discards qualifiers from pointer 
target type
openssl.c:217: warning: assignment discards qualifiers from pointer 
target type
openssl.c:219: warning: assignment discards qualifiers from pointer 
target type
openssl.c:223: warning: assignment discards qualifiers from pointer 
target type
openssl.c:226: warning: assignment discards qualifiers from pointer 
target type

openssl.c: In function 'ssl_check_host':
openssl.c:311: error: 'STACK' undeclared (first use in this function)
openssl.c:311: error: (Each undeclared identifier is reported only once
openssl.c:311: error: for each function it appears in.)
openssl.c:311: error: 'gens' undeclared (first use in this function)
openssl.c: At top level:
openssl.c:499: error: expected declaration specifiers or '...' before 
'STACK'

openssl.c: In function 'smime_verify':
openssl.c:508: error: 'STACK' undeclared (first use in this function)
openssl.c:508: error: 'certs' undeclared (first use in this function)
openssl.c:508: error: 'gens' undeclared (first use in this function)
openssl.c:555: error: 'chain' undeclared (first use in this function)
openssl.c: In function 'cverify':
openssl.c:617: error: 'STACK' undeclared (first use in this function)
openssl.c:617: error: 'chain' undeclared (first use in this function)
openssl.c:649: error: too many arguments to function 'smime_verify'
openssl.c: In function 'smime_encrypt':
openssl.c:690: error: 'STACK' undeclared (first use in this function)
openssl.c:690: error: 'certs' undeclared (first use in this function)
openssl.c: In function 'smime_certsave':
openssl.c:953: error: 'STACK' undeclared (first use in this function)
openssl.c:953: error: 'certs' undeclared (first use in this function)
openssl.c:955: error: 'chain' undeclared (first use in this function)
make: *** [openssl.o] Error 1
error: Bad exit status from /openpkg/RPM/TMP/rpm-tmp.7869 (%build)


RPM build errors:
   Bad exit status from /openpkg/RPM/TMP/rpm-tmp.7869 (%build)


__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


Re: OpenPKG-4: problem compiling nail on Solaris 10 x86

2010-04-16 Thread Olivier Fournier
   X509_STORE  *store;
   char*ca_dir, *ca_file;

@@ -687,7 +710,11 @@
   X509*cert;
   PKCS7   *pkcs7;
   BIO *bb, *yb;
+#ifdef HAVE_STACK_OF
+STACK_OF(X509)  *certs;
+#else
   STACK   *certs;
+#endif
   EVP_CIPHER  *cipher;

   certfile = expand((char *)certfile);
@@ -950,9 +977,14 @@
   off_t   size;
   BIO *fb, *pb;
   PKCS7   *pkcs7;
+#ifdef HAVE_STACK_OF
+STACK_OF(X509)  *certs;
+STACK_OF(X509)  *chain = NULL;
+#else
   STACK   *certs;
-   X509*cert;
   STACK   *chain = NULL;
+#endif
+X509*cert;
   enum okay   ok = OKAY;

   message_number = n;



Olivier Fournier wrote:

Hi All,

I have a problem compiling nail under Solaris 10 x86 (see log below). 
Is it related to the new version of OpenSSL ?


How can I fix this issue?

Thanks a lot in advance.

Regards,
Olivier


/openpkg/bin/cc -O2 -pipe -I/openpkg/include 
-DMAILRC='/openpkg/etc/nail/nail.rc' -DMAILSPOOL='/var/mail' 
-DSENDMAIL='/openpkg/sbin/sendmail' -c openssl.c
openssl.c:108: error: expected declaration specifiers or '...' before 
'STACK'

openssl.c: In function 'ssl_select_method':
openssl.c:215: warning: assignment discards qualifiers from pointer 
target type
openssl.c:217: warning: assignment discards qualifiers from pointer 
target type
openssl.c:219: warning: assignment discards qualifiers from pointer 
target type
openssl.c:223: warning: assignment discards qualifiers from pointer 
target type
openssl.c:226: warning: assignment discards qualifiers from pointer 
target type

openssl.c: In function 'ssl_check_host':
openssl.c:311: error: 'STACK' undeclared (first use in this function)
openssl.c:311: error: (Each undeclared identifier is reported only once
openssl.c:311: error: for each function it appears in.)
openssl.c:311: error: 'gens' undeclared (first use in this function)
openssl.c: At top level:
openssl.c:499: error: expected declaration specifiers or '...' before 
'STACK'

openssl.c: In function 'smime_verify':
openssl.c:508: error: 'STACK' undeclared (first use in this function)
openssl.c:508: error: 'certs' undeclared (first use in this function)
openssl.c:508: error: 'gens' undeclared (first use in this function)
openssl.c:555: error: 'chain' undeclared (first use in this function)
openssl.c: In function 'cverify':
openssl.c:617: error: 'STACK' undeclared (first use in this function)
openssl.c:617: error: 'chain' undeclared (first use in this function)
openssl.c:649: error: too many arguments to function 'smime_verify'
openssl.c: In function 'smime_encrypt':
openssl.c:690: error: 'STACK' undeclared (first use in this function)
openssl.c:690: error: 'certs' undeclared (first use in this function)
openssl.c: In function 'smime_certsave':
openssl.c:953: error: 'STACK' undeclared (first use in this function)
openssl.c:953: error: 'certs' undeclared (first use in this function)
openssl.c:955: error: 'chain' undeclared (first use in this function)
make: *** [openssl.o] Error 1
error: Bad exit status from /openpkg/RPM/TMP/rpm-tmp.7869 (%build)


RPM build errors:
   Bad exit status from /openpkg/RPM/TMP/rpm-tmp.7869 (%build)




__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


Re: Introducing OpenPKG 4.x

2010-02-11 Thread Olivier Fournier
We are exactly in the same situation. Due to the lack of support and 
problem handling appearing with OpenPKG-4, we are now intensively 
looking for alternatives. We can not avoid waiting weeks and weeks for a 
problem to be handled and (eventually) solved. Hopefully it will get 
better in the future...

__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


OpenPKG-4: why can't I retrieve packages through HTTP?

2010-02-08 Thread Olivier Fournier
Hi all,

I am trying to download packages and source packages from different remote
HTTP repositories, but it doesn't work as expected...

open...@lab$ openpkg -v
OpenPKG-CURRENT (4.0.2)

open...@lab$ openpkg rpm -Uvh
http://download.openpkg.org/packages/current/source/BASE/adns-1.4-20080101.src.rpm
= error: open of http://UID:UID.UID@
download.openpkg.org/packages/current/source/BASE/adns-1.4-20080101.src.rpmfailed:
No such file or directory

but...

open...@lab$ openpkg curl
http://download.openpkg.org/packages/current/source/BASE/adns-1.4-20080101.src.rpm
= works like a charm

Am I missing something / doing something wrong? With previous OpenPKG
releases this feature was working as expected...

Thanks a lot in advance for your answer,
Olivier


Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch

2010-01-27 Thread Olivier Fournier
Thanks for you answer Jeff. But I also don't know RPM macros and Lua 
well enough to debug this issue.


But anyway, am I the only one to have this kind of problems while 
bootstrapping all my servers?


Olivier
__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch

2010-01-26 Thread Olivier Fournier

Hi all,

actually, I could reproduce exactly the same error while bootstrapping 
OpenPKG-4 under Solaris 10 (amd64). So I decided to investigate a bit 
more, and here are my results: at the end of the compilation, just 
before the RPM files are created, I can see a lot of errors related to 
Lua. So my question: is it a bug or am I missing something on all my 
systems?


If you need the complete bootstrap logs (for Debian and Solaris), feel 
free to ask.


Thanks a lot in advance for your help,
Olivier

=
Executing(%install): env -i OPENPKG_BOOT=1 
/tmp/openpkg-4.0.1-20100104-buildroot/openpkg/lib/openpkg/bash --norc 
--noprofile --posix -e /tmp/rpm-tmp.23037

Processing files: openpkg-4.0.1-20100104
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 4 (empty)
 3   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 5   (empty)
 4 (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 6 (empty)
 5   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 7   (empty)
 6 (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 8 (empty)
 7   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

 9   (empty)
 8 (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

10 (empty)
 9   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

11   (empty)
10 (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

12 (empty)
11   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

13   (empty)
12 (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

14 (empty)
13   (empty)
error: Macro %_rpmdir failed to expand
error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via 
realpath(3): No such file or directory

15   (empty)
14 (empty)
error: Macro %_rpmdir failed to expand
error: Recursion depth(17) greater than max(16)
15   (empty)
14   
error: Macro %_rpmdir has unterminated body

14 (empty)
error: Recursion depth(17) greater than max(16)
15   (empty)
error: Macro %_rpmdir has unterminated body
15   (empty)
error: Recursion depth(17) greater than max(16)
error: Recursion depth(17) greater than max(16)
error: Recursion depth(17) greater than max(16)
15   (empty)
14 (empty)
13   (empty)
12 (empty)
11   (empty)
10 (empty)
 9   (empty)
 8 (empty)
 7   (empty)
 6 (empty)
 5   (empty)
 4 (empty)
 3   (empty)
 2 (empty)
 1   (empty)
 0 (empty)
error: Could not open : No such file or directory
=
__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch

2010-01-25 Thread Olivier Fournier

Ralf S. Engelschall wrote:

I've done an installation under Debian 5.0 myself recently
without problems. Interesting that it caused problems for you.
  
My tests were done on two fresh-installed Debian 5.0.3 on the following 
architectures:


   * Linux debian-test 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC
 2009 x86_64 GNU/Linux
   * Linux debian-test 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00
 UTC 2009 i686 GNU/Linux

And the results were exactly the same = permissions problems.

It should not. The warnings result because of the wrong ownerships on
the files. Why the ownerships are wrong I don't know. Have you specified
some strange --user or --group options during bootstrapping?
  

Here is my bootstraping command:
sh openpkg-4.0.1-20100104.src.sh \
   --prefix=/openpkg --tag=openpkg \
   --user=openpkg --group=openpkg

so no strange user or group option.

Also this is incorrect. There ownerships were not correctly set for you
  
as it seems. I've to check this myself under Debian 5.0 again...


  

Would be great if you could test again with an up to date Debian version.

Thanks a lot in advance.
Olivier
__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch

2010-01-18 Thread Olivier Fournier

Hi everyone,

here are my results of the test-driving procedure on a fresh installed 
Debian Lenny.


Can someone explain me the following things:

- Why does OpenPKG need to be bootstrapped twice in order to get it to 
work without warnings?
- Why do the permissions of the license file have to be manually 
adjusted in order to activate a license?

- Why do so many files belong to root after a fresh installation?

Thanks and Regards,
Olivier

-

# system information
r...@lab:/var/tmp# uname -a
Linux lab.test 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC 2009 
i686 GNU/Linux


r...@lab:/var/tmp# cat /etc/debian_version
5.0.3

# download latest OpenPKG framework bootstrap sources
r...@lab:/var/tmp# curl -LO http://openpkg.org/go/download/openpkg.src.sh
 % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
Dload  Upload   Total   SpentLeft  
Speed
 2 43.6M2  949k0 0   262k  0  0:02:50  0:00:03  
0:02:47  314k


# bootstrap OpenPKG instance
r...@lab:/var/tmp# sh openpkg.src.sh   --prefix=/openpkg --tag=openpkg
   --user=openpkg --group=openpkg
OpenPKG CURRENT Source Bootstrap Package, version 20100104
Building for prefix /openpkg on current platform
++ extracting OpenPKG source distribution
++ building OpenPKG binary distribution
OpenPKG Bootstrap Procedure
++ bootstrap version: 4.0.1-20100104
...

# install newly produced package
r...@lab:/var/tmp# sh openpkg-*-openpkg.sh
OpenPKG CURRENT Binary Bootstrap Package, version package openpkg is not 
installed

Built for prefix /openpkg on target platform ix86-debian5.0
++ hooking OpenPKG instance into system environment
++ creating OpenPKG instance root directory /openpkg
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
++ fixating OpenPKG instance filesystem hierarchy
++ post-processing OpenPKG bootstrap installation
...

# switch to openpkg user = why these warnings?
r...@lab:/var/tmp# su - openpkg
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file

open...@lab$

# rebuild openpkg = why is it needed? Don't I have already the latest 
version?

r...@lab:/var/tmp# /openpkg/bin/openpkg build openpkg | sh
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
 
http://download.openpkg.org/framework/release/source/openpkg-4.0.1-20100104.src.rpm 

openpkg:WARNING: invalid owner user id 0 (expected 1001) on 
configuration file /openpkg/etc/openpkg/managers -- ignoring file
## 
3.7%

...

# switch to openpkg user = OK, no more warning
r...@lab:/var/tmp# su - openpkg
open...@lab$

# activate community license = permission denied
open...@lab$ openpkg license activate COMMUNITY
/openpkg/libexec/openpkg/license: line 167: 
/openpkg/etc/openpkg/license: Permission denied

openpkg:license:ERROR: failed to activate license under id COMMUNITY

# change ownership of license file
r...@lab:/var/tmp# chown -R openpkg:openpkg /openpkg/etc/openpkg/license

# activate community license = OK
open...@lab$ openpkg license activate COMMUNITY

# files belonging to root. Is it normal?
r...@lab:/var/tmp# find /openpkg/ -user root
/openpkg/.bash_login
/openpkg/etc/rc.conf
/openpkg/etc/openpkg/register.tran
/openpkg/etc/openpkg/managers.rpmorig
/openpkg/etc/openpkg/rpmlua.rpmorig
/openpkg/etc/openpkg/rpmpopt.rpmorig
/openpkg/etc/openpkg/register.prep
/openpkg/etc/openpkg/platform.rpmorig
/openpkg/etc/openpkg/register.util

Service supervision within OpenPKG

2008-04-03 Thread Olivier Fournier
Hello everyone

I need your experience in service supervision. At the
moment, we are using OpenPKG under both Solaris 10 and
RHEL5. We are now looking for a standard way to
supervise our daemons and services under these two
platforms. Till now we had following approach:
everytime we had to install and configure a new
service, we chose a one-time solution for the service
supervision... It means that, at the moment, we are
fighting with at least tree different approaches:

- Solaris Management Facility (SMF), only applicable
under Solaris. To use this solution, we need to modify
the OpenPKG rc scripts of the service to tell OpenPKG
to not take care of this service anymore, which is not
so clean
- Daemontools, for specific services such as djbdns
- Runit, for OpenVPN and other things

My question is following: what kind of service
supervision are you using in your infrastructure? I am
aware that there is no perfect solution, but my goal
is to define a standard approach for well known
services. We will always find exceptions, but we will
handle them separately.

Thank you in advance for a small feedback.

Best Regards
Olivier


  
_ 
Envoyez avec Yahoo! Mail. Plus de moyens pour rester en contact. 
http://mail.yahoo.fr
__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org


RE : Problem by compiling inetutils on Solaris 10

2007-10-11 Thread Olivier Fournier
Some news:

I applied the patch I found here:
http://osdir.com/ml/gnu.inetutils.bugs/2006-11/msg9.html

... but another problem happens (I could not determine
if it happens before or after the old one)

-
make[2]: Entering directory
`/opt/openpkg/RPM/TMP/inetutils-1.5/libinetutils'
if /openpkg/bin/cc -DHAVE_CONFIG_H -I. -I. -I..
-I../headers -I../lib -I../lib 
-DPATH_TTY_PFX=\/dev/\ -DPATH_DEVNULL=\/dev/null\ 
 -I/openpkg/include/ncurses -I/openpkg/include
-D_REENTRANT  -O2 -pipe -MT localhost.o -MD -MP -MF
.deps/localhost.Tpo -c -o localhost.o localhost.c; \
then mv -f .deps/localhost.Tpo
.deps/localhost.Po; else rm -f
.deps/localhost.Tpo; exit 1; fi
In file included from /usr/include/sys/socket.h:40,
 from localhost.c:36:
/usr/include/sys/socket_impl.h:44: error: duplicate
'unsigned'
/usr/include/sys/socket_impl.h:44: error: two or more
data types in declaration specifiers
In file included from /usr/include/sys/socket.h:45,
 from localhost.c:36:
/usr/include/netinet/in.h:54: error: two or more data
types in declaration specifiers
make[2]: *** [localhost.o] Error 1
make[2]: Leaving directory
`/opt/openpkg/RPM/TMP/inetutils-1.5/libinetutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/opt/openpkg/RPM/TMP/inetutils-1.5'
make: *** [all] Error 2
-

Any help will be appreciated.

Regards
Olivier

--- Olivier Fournier [EMAIL PROTECTED] a écrit
:

 Hi everyone,
 
 I try to compile inetutils on an OpenPKG instance
 running on Solaris 10, but I receive following
 error:
 
 -
 if /openpkg/bin/cc -DHAVE_CONFIG_H -I. -I. -I..
 -I../headers -I../lib -I../lib 
 -DPATH_TTY_PFX=\/dev/\
 -DPATH_DEVNULL=\/dev/null\ 
  -I/openpkg/include/ncurses -I/openpkg/include
 -D_REENTRANT  -O2 -pipe -MT logwtmpko.o -MD -MP -MF
 .deps/logwtmpko.Tpo -c -o logwtmpko.o logwtmpko.c;
 then mv -f .deps/logwtmpko.Tpo
 .deps/logwtmpko.Po; else rm -f
 .deps/logwtmpko.Tpo; exit 1; fi
 In file included from logwtmpko.c:2:
 logwtmp.c: In function 'logwtmp_keep_open':
 logwtmp.c:115: warning: incompatible implicit
 declaration of built-in function 'bzero'
 if /openpkg/bin/cc -DHAVE_CONFIG_H -I. -I. -I..
 -I../headers -I../lib -I../lib 
 -DPATH_TTY_PFX=\/dev/\
 -DPATH_DEVNULL=\/dev/null\ 
  -I/openpkg/include/ncurses -I/openpkg/include
 -D_REENTRANT  -O2 -pipe -MT setsig.o -MD -MP -MF
 .deps/setsig.Tpo -c -o setsig.o setsig.c;
 then mv -f .deps/setsig.Tpo
 .deps/setsig.Po; else rm -f .deps/setsig.Tpo;
 exit
 1; fi
 setsig.c:34: error: expected '=', ',', ';', 'asm' or
 '__attribute__' before 'setsig'
 make[2]: *** [setsig.o] Error 1
 make[1]: *** [all-recursive] Error 1
 make: *** [all] Error 2
 error: Bad exit status from
 /openpkg/RPM/TMP/rpm-tmp.13342 (%build)
 
 
 RPM build errors:
 Bad exit status from
 /openpkg/RPM/TMP/rpm-tmp.13342 (%build)
 -
 
 I was trying to install nagios on my machine. All
 the
 other dependencies compiled well but with this one I
 have a problem.
 
 Could anyone help me to solve this problem ?
 
 Thank you very much in advance
 
 Regards
 Olivier
 
 
  

_
 
 Ne gardez plus qu'une seule adresse mail ! Copiez
 vos mails vers Yahoo! Mail 

__
 OpenPKG
 http://openpkg.org
 User Communication List 
 openpkg-users@openpkg.org
 



  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 
__
OpenPKG http://openpkg.org
User Communication List  openpkg-users@openpkg.org