From kakyea at gmail.com Tue Feb 5 20:48:28 2013 From: kakyea at gmail.com (Kafui Akyea) Date: Tue, 5 Feb 2013 14:48:28 -0500 Subject: [csw-users] fontconfig fc-cache to Speed Up RRDgraph in Cacti installation on Solaris Message-ID: Hi I found this out and i believe it might be useful to other folks who are trying to install Cacti on Solaris and have built their SAMP using packages from OpenCSW. The problem i had was with the graphs in Cacti being too slow to show up sometimes taking up to 20 seconds. These are the steps i took to fix it on my installation after much googling. 1. Use fc-cache -f -v to rebuild the font cache files /opt/csw/bin/fc-cache -f -v 2. Change the permissions on the fontconfig folder to make it writeable chmod 777 /var/opt/csw/cache/fontconfig after refresh the Cacti page to see if the graphs display faster. If not then 3. Change the permissions on the cache folder to make it writeable chmod 777 /var/opt/csw/cache Hope it helps if you are having the same problem. Kafui -------------- next part -------------- An HTML attachment was scrubbed... URL: From lassmichinruhe at rz-amper.de Tue Feb 5 22:22:23 2013 From: lassmichinruhe at rz-amper.de (Markus Sonnenberg) Date: Tue, 05 Feb 2013 22:22:23 +0100 Subject: [csw-users] fontconfig fc-cache to Speed Up RRDgraph in Cacti installation on Solaris In-Reply-To: References: Message-ID: <5111780F.2070302@rz-amper.de> Hi Kafui, thanks for sharing. i followed your instructions and indeed it seems to build the graphs a bit faster as usually. regards Markus ct, On 2/5/2013 8:48 PM, Kafui Akyea wrote: > Hi > > I found this out and i believe it might be useful to other folks who are > trying to install Cacti on Solaris > and have built their SAMP using packages from OpenCSW. The problem i had > was with the graphs in Cacti > being too slow to show up sometimes taking up to 20 seconds. These are > the steps i took to fix it on my installation > after much googling. > > 1. Use |fc-cache -f -v| to rebuild the font cache files > /opt/csw/bin/fc-cache -f -v > > 2. Change the permissions on the fontconfig folder to make it writeable > chmod 777 /var/opt/csw/cache/fontconfig > after refresh the Cacti page to see if the graphs display faster. If not > then > > 3. Change the permissions on the cache folder to make it writeable > chmod 777 /var/opt/csw/cache > > Hope it helps if you are having the same problem. > > Kafui > > > > > > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users -- Das Abspringen einer Begrenzungsmauer dient nicht dem direkten Zur?cklegen des Arbeitsweges. http://www.rz-amper.de From emaros at ligo.caltech.edu Wed Feb 13 23:06:08 2013 From: emaros at ligo.caltech.edu (Edward Maros) Date: Wed, 13 Feb 2013 14:06:08 -0800 Subject: [csw-users] 64bit g++ 4.7.2 exception handling ... Message-ID: <511C0E50.7050901@ligo.caltech.edu> I have a very simple piece of code that behaves differently depending if it is compiled 32bit vs 64bit. Is this an issue with the compiler or how it was packaged? #include int main( int, char** ) { try { throw std::runtime_error( "Catch me if you can!" ); } catch(...) { return 0; } return 1; } When compiled and executed using "g++ t.cc", the return status is 0 When compiled and executed using "g++ -m64 t.cc", the return status is, terrminate called after throwing an instance of 'std::runtime_error' terminate called recursively Abort (core dumped) -bash-3.2$ uname -a SunOS x4270-qfs 5.10 Generic_147441-27 i86pc i386 i86pc -bash-3.2$ g++ --version g++ (GCC) 4.7.2 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -bash-3.2$ which g++ /opt/csw/bin/g++ Thanks, Ed From maciej at opencsw.org Wed Feb 13 23:57:02 2013 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=) Date: Wed, 13 Feb 2013 22:57:02 +0000 Subject: [csw-users] 64bit g++ 4.7.2 exception handling ... In-Reply-To: <511C0E50.7050901@ligo.caltech.edu> References: <511C0E50.7050901@ligo.caltech.edu> Message-ID: 2013/2/13 Edward Maros > terrminate called after throwing an instance of 'std::runtime_error' > terminate called recursively > Abort (core dumped) I am able to reproduce this, only on Intel. The Sparc version doesn't suffer from this problem. I did some searching around and found this bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53730 The solution is rather unexciting: "Yes, switching away from the gold linker and rebuilding gcc solves the problem!" We aren't using the gold linker in our build, so maybe it's a similar problem with the sun linker? Obviously it's only a guess. I'll try to get that resolved, but I'm currently spread very thin, so I can't promise fast progress. Maciej From emaros at ligo.caltech.edu Thu Feb 14 00:21:58 2013 From: emaros at ligo.caltech.edu (Edward Maros) Date: Wed, 13 Feb 2013 15:21:58 -0800 Subject: [csw-users] 64bit g++ 4.7.2 exception handling ... In-Reply-To: References: <511C0E50.7050901@ligo.caltech.edu> Message-ID: <511C2016.2020401@ligo.caltech.edu> On 2/13/13 2:57 PM, Maciej (Matchek) Blizi?ski wrote: > 2013/2/13 Edward Maros >> terrminate called after throwing an instance of 'std::runtime_error' >> terminate called recursively >> Abort (core dumped) > I am able to reproduce this, only on Intel. The Sparc version doesn't > suffer from this problem. > > I did some searching around and found this bug: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53730 The solution is > rather unexciting: "Yes, switching away from the gold linker and > rebuilding gcc solves the problem!" > > We aren't using the gold linker in our build, so maybe it's a similar > problem with the sun linker? Obviously it's only a guess. > > I'll try to get that resolved, but I'm currently spread very thin, so > I can't promise fast progress. > > Maciej Thank you for looking into this. Currently it is not critical since I can build my software as a 32bit executable. I look forward to the day when it can be a 64bit executable. Ed From jh at opencsw.org Thu Feb 14 17:31:49 2013 From: jh at opencsw.org (Jan Holzhueter) Date: Thu, 14 Feb 2013 17:31:49 +0100 Subject: [csw-users] 64bit g++ 4.7.2 exception handling ... In-Reply-To: References: <511C0E50.7050901@ligo.caltech.edu> Message-ID: <511D1175.20105@opencsw.org> Hi, Am 13.02.13 23:57, schrieb Maciej (Matchek) Blizi?ski: > 2013/2/13 Edward Maros >> terrminate called after throwing an instance of 'std::runtime_error' >> terminate called recursively >> Abort (core dumped) > > I am able to reproduce this, only on Intel. The Sparc version doesn't > suffer from this problem. > > I did some searching around and found this bug: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53730 The solution is > rather unexciting: "Yes, switching away from the gold linker and > rebuilding gcc solves the problem!" > > We aren't using the gold linker in our build, so maybe it's a similar > problem with the sun linker? Obviously it's only a guess. we switched back to gld on x86 didn't we. :) It's probably fine with sun linker but then we have the other problem which I don't remember what it was atm :) If I have some spare time will look into this too Greetings Jan From jh at opencsw.org Thu Feb 14 17:36:01 2013 From: jh at opencsw.org (Jan Holzhueter) Date: Thu, 14 Feb 2013 17:36:01 +0100 Subject: [csw-users] 64bit g++ 4.7.2 exception handling ... In-Reply-To: <511D1175.20105@opencsw.org> References: <511C0E50.7050901@ligo.caltech.edu> <511D1175.20105@opencsw.org> Message-ID: <511D1271.5030100@opencsw.org> Am 14.02.13 17:31, schrieb Jan Holzhueter: > Hi, > > Am 13.02.13 23:57, schrieb Maciej (Matchek) Blizi?ski: >> 2013/2/13 Edward Maros >>> terrminate called after throwing an instance of 'std::runtime_error' >>> terminate called recursively >>> Abort (core dumped) >> >> I am able to reproduce this, only on Intel. The Sparc version doesn't >> suffer from this problem. >> >> I did some searching around and found this bug: >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53730 The solution is >> rather unexciting: "Yes, switching away from the gold linker and >> rebuilding gcc solves the problem!" >> >> We aren't using the gold linker in our build, so maybe it's a similar >> problem with the sun linker? Obviously it's only a guess. > > we switched back to gld on x86 didn't we. :) oh that was gas/as nevermind :) Greetings Jan From maciej at opencsw.org Wed Feb 20 20:17:53 2013 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=) Date: Wed, 20 Feb 2013 19:17:53 +0000 Subject: [csw-users] An update to the kiel catalog Message-ID: Heads up for those subscribing to the kiel catalog: I'm currently running an integration from the unstable catalog. There are updates or new packages for 100 different pieces of software, 330+ packages total. Some highlights: GCC 4.7.2, PHP 5.3.21, Samba 3.6.10, MySQL 5.5.30 and many Perl modules. If you're curious which exact packages were updated, visit our feeds page, where you'll always get the newest information: http://www.opencsw.org/feeds/ The update will be live on the master mirror in few hours, and later on external mirrors, the feed will be updated after the master mirror is. Enjoy the updates! If you see any problems, report bugs or talk to us on #opencsw on Freenode. Maciej From jcraig at opencsw.org Thu Feb 21 20:05:54 2013 From: jcraig at opencsw.org (Jonathan Craig) Date: Thu, 21 Feb 2013 14:05:54 -0500 Subject: [csw-users] Puppet in an OpenCSW environment Message-ID: I'm interested in using puppet to begin managing our server infrastructure and looking to the community for insight. We currently have 450 servers (250 Solaris 10/11, 50 SUSE, 150 RedHat) to manage. The questions I'm grappling with are: 1) Puppet 2.7 vs 3.0 2) Free vs Commercial 3) OpenCSW vs GEM install 4) Should I run the master on Solaris or use RedHat with the expectation that it will be better supported within the Puppet community So, is anyone using the puppet/puppet3 CSW module; in production? How do you layout your directories ? - Use CSW standards (/etc/opt/CSW, /var/opt/CSW, ...) ? - Use standard puppet directories (/etc, /var, ...) Are you managing Solaris 11 Boxes? ? - What package providers do you use? ? - pkgutil ? - pkg ? - sun ?? - blastwave ?? - sunfreeware ? - any gotchas you know of How do you handle your internal packages (Business apps, admin scripts/tools)? ? - package them with platform specific packaging and manage with standard providers ? - use some other packaging and/or provider Thanks in advance, and I plan to share a summary for others who may be interested. Jon Craig From gadavis at opencsw.org Thu Feb 21 20:28:32 2013 From: gadavis at opencsw.org (Geoff Davis) Date: Thu, 21 Feb 2013 11:28:32 -0800 Subject: [csw-users] Puppet in an OpenCSW environment In-Reply-To: References: Message-ID: <899D0FDE-7EF0-42A4-A5E6-6993ACE4F922@opencsw.org> Hi Jon, I initially started with Puppet Open Source using the OpenCSW packages. I'm now using Puppet Enterprise because I just wanted the silly thing up and running, rather than trying to configure all of the moving parts. The PE console ONLY runs on Linux, either Ubuntu or RHEL variants. Solaris is supported as a managed node only, not as an admin node, puppet master node, or console. I had an open source puppet master running on a Solaris 10 box using the OpenCSW package. The whole Phusion Passenger bit was a pain to get working with OpenCSW Apache, and I didn't even get the console out of the deal, just the puppet master functionality itself. When I went Puppet Enterprise, I used the PE installers for Solaris and removed my OpenCSW packages. I make heavy use of the pkgutil package provider for Puppet for my Solaris 10 boxes, but we don't do much in the way of custom packaging on that platform. For my RHEL boxes, I have a few custom packages and run my own yum repository. I realize you've got a Solaris 11 deployment, but if you have Solaris 10 sitting around I've done quite a few fork-and-modify of existing Puppet modules as well as develop a few of my own. Some of these modules were designed originally to support Debian/RedHat, but I've hacked in OpenCSW support. They are up on GitHub, and I'll take any pull requests. https://github.com/geoffdavis/puppet-snmp https://github.com/UCSD-ANF/puppet-apache https://github.com/UCSD-ANF/puppet-logrotate https://github.com/UCSD-ANF/puppet-perl https://github.com/UCSD-ANF/puppet-php https://github.com/UCSD-ANF/puppet-rrdtool https://github.com/UCSD-ANF/puppetlabs-ntp On Feb 21, 2013, at 11:05 AM, Jonathan Craig wrote: > I'm interested in using puppet to begin managing our server > infrastructure and looking to the community for insight. We currently > have 450 servers (250 Solaris 10/11, 50 SUSE, 150 RedHat) to manage. > The questions I'm grappling with are: > > 1) Puppet 2.7 vs 3.0 > 2) Free vs Commercial > 3) OpenCSW vs GEM install > 4) Should I run the master on Solaris or use RedHat with the > expectation that it will be better supported within the Puppet > community > > So, is anyone using the puppet/puppet3 CSW module; in production? > > How do you layout your directories > ? - Use CSW standards (/etc/opt/CSW, /var/opt/CSW, ...) > ? - Use standard puppet directories (/etc, /var, ...) > > Are you managing Solaris 11 Boxes? > ? - What package providers do you use? > ? - pkgutil > ? - pkg > ? - sun > ?? - blastwave > ?? - sunfreeware > ? - any gotchas you know of > > How do you handle your internal packages (Business apps, admin scripts/tools)? > ? - package them with platform specific packaging and manage with > standard providers > ? - use some other packaging and/or provider > > Thanks in advance, and I plan to share a summary for others who may be > interested. > > Jon Craig > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.biran at alcatel-lucent.com Fri Feb 22 22:56:41 2013 From: yahav.biran at alcatel-lucent.com (BIRAN, Yahav (Yahav)) Date: Fri, 22 Feb 2013 21:56:41 +0000 Subject: [csw-users] starting up with open CSW Message-ID: Hello All: I have a pre compiled package for Solaris 10 / Sparc that I would like to publish on one the public mirrors. Is there any good getting started tutorials one can use other than http://www.opencsw.org/manual/for-administrators/getting-started.html? I am looking for something more for the specific technical details on how/what to pack? And how to publish to your repository ? (I guess a user is required as well). I was doing some reading on the tutorial above and some more pages on the opencsw.org. I must say it it looks very nice and organized. Thank you Yahav -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.biran at alcatel-lucent.com Fri Feb 22 23:45:25 2013 From: yahav.biran at alcatel-lucent.com (BIRAN, Yahav (Yahav)) Date: Fri, 22 Feb 2013 22:45:25 +0000 Subject: [csw-users] finding the .CSW files Message-ID: In the search page http://www.opencsw.org/search/zabbix_agent/ The following files are: Path /etc/opt/csw/zabbix_agent.conf.CSW /etc/opt/csw/zabbix_agentd.conf.CSW /opt/csw/bin/amd64/zabbix_get /opt/csw/bin/amd64/zabbix_sender /opt/csw/bin/pentium_pro/zabbix_get /opt/csw/bin/pentium_pro/zabbix_sender /opt/csw/bin/zabbix_get /opt/csw/bin/zabbix_sender /opt/csw/sbin/amd64/zabbix_agent /opt/csw/sbin/amd64/zabbix_agentd /opt/csw/sbin/pentium_pro/zabbix_agent /opt/csw/sbin/pentium_pro/zabbix_agentd /opt/csw/sbin/zabbix_agent /opt/csw/sbin/zabbix_agentd /opt/csw/share/doc/zabbix_agent/license /opt/csw/share/man/man1/zabbix_get.1 /opt/csw/share/man/man1/zabbix_sender.1 /opt/csw/share/man/man8/zabbix_agentd.8 But on the server after the install: -bash-3.2$ sudo pkgutil -y -i zabbix_agent Solving needed dependencies ... Solving dependency order ... 2 CURRENT packages: CSWcommon-1.5,REV=2010.12.11 CSWlibiconv2-1.14,REV=2011.08.07 Install 1 NEW packages: CSWzabbix-agent-1.8.10,REV=2012.03.16 (opencsw/testing) Total size: 255.2 KB => Fetching CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... => Installing CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... Please see /opt/csw/share/doc/zabbix_agent/license for license information. Installation of was successful. I get the following: -bash-3.2$ sudo find /opt/csw/ | grep -i zabbix /opt/csw/share/doc/zabbix_agent /opt/csw/share/doc/zabbix_agent/license /opt/csw/share/man/man8/zabbix_agentd.8 /opt/csw/share/man/man1/zabbix_sender.1 /opt/csw/share/man/man1/zabbix_get.1 /opt/csw/bin/zabbix_get /opt/csw/bin/zabbix_sender /opt/csw/sbin/zabbix_agent /opt/csw/sbin/zabbix_agentd -bash-3.2$ sudo find /etc/ | grep -i zabbix /etc/zabbix /etc/zabbix/zabbix_agentd.HOST /etc/zabbix/hostparms.HOST /etc/zabbix/userparms /etc/init.d/zabbix_agentd -bash-3.2$ I would expect to see the /etc/opt/csw/zabbix_agent.conf.CSW and /etc/opt/csw/zabbix_agentd.conf.CSW How one can view these files? Thank you, yahav -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Sat Feb 23 00:10:21 2013 From: bwalton at opencsw.org (Ben Walton) Date: Fri, 22 Feb 2013 23:10:21 +0000 Subject: [csw-users] finding the .CSW files In-Reply-To: References: Message-ID: On Fri, Feb 22, 2013 at 11:09 PM, Ben Walton wrote: > Hi Yahav, > > > On Fri, Feb 22, 2013 at 10:45 PM, BIRAN, Yahav (Yahav) > wrote: >> In the search page http://www.opencsw.org/search/zabbix_agent/ >> The following files are: >> >> Path >> /etc/opt/csw/zabbix_agent.conf.CSW >> /etc/opt/csw/zabbix_agentd.conf.CSW >> /opt/csw/bin/amd64/zabbix_get >> /opt/csw/bin/amd64/zabbix_sender >> /opt/csw/bin/pentium_pro/zabbix_get >> /opt/csw/bin/pentium_pro/zabbix_sender >> /opt/csw/bin/zabbix_get >> /opt/csw/bin/zabbix_sender >> /opt/csw/sbin/amd64/zabbix_agent >> /opt/csw/sbin/amd64/zabbix_agentd >> /opt/csw/sbin/pentium_pro/zabbix_agent >> /opt/csw/sbin/pentium_pro/zabbix_agentd >> /opt/csw/sbin/zabbix_agent >> /opt/csw/sbin/zabbix_agentd >> /opt/csw/share/doc/zabbix_agent/license >> /opt/csw/share/man/man1/zabbix_get.1 >> /opt/csw/share/man/man1/zabbix_sender.1 >> /opt/csw/share/man/man8/zabbix_agentd.8 >> >> But on the server after the install: >> >> -bash-3.2$ sudo pkgutil -y -i zabbix_agent >> Solving needed dependencies ... >> Solving dependency order ... >> 2 CURRENT packages: >> CSWcommon-1.5,REV=2010.12.11 >> CSWlibiconv2-1.14,REV=2011.08.07 >> Install 1 NEW packages: >> CSWzabbix-agent-1.8.10,REV=2012.03.16 (opencsw/testing) >> Total size: 255.2 KB >> => Fetching CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... >> >> => Installing CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... >> Please see /opt/csw/share/doc/zabbix_agent/license for license information. >> >> Installation of was successful. >> >> I get the following: >> >> -bash-3.2$ sudo find /opt/csw/ | grep -i zabbix >> /opt/csw/share/doc/zabbix_agent >> /opt/csw/share/doc/zabbix_agent/license >> /opt/csw/share/man/man8/zabbix_agentd.8 >> /opt/csw/share/man/man1/zabbix_sender.1 >> /opt/csw/share/man/man1/zabbix_get.1 >> /opt/csw/bin/zabbix_get >> /opt/csw/bin/zabbix_sender >> /opt/csw/sbin/zabbix_agent >> /opt/csw/sbin/zabbix_agentd >> -bash-3.2$ sudo find /etc/ | grep -i zabbix >> /etc/zabbix >> /etc/zabbix/zabbix_agentd.HOST >> /etc/zabbix/hostparms.HOST >> /etc/zabbix/userparms >> /etc/init.d/zabbix_agentd >> -bash-3.2$ >> >> I would expect to see the /etc/opt/csw/zabbix_agent.conf.CSW >> and /etc/opt/csw/zabbix_agentd.conf.CSW >> >> How one can view these files? > > What does this show: > pkgchk -l CSWgit | grep Pathname Sorry, please use CSWzabbix-agent in the command. Thanks -Ben From dam at opencsw.org Sat Feb 23 14:31:27 2013 From: dam at opencsw.org (Dagobert Michelsen) Date: Sat, 23 Feb 2013 14:31:27 +0100 Subject: [csw-users] finding the .CSW files In-Reply-To: References: Message-ID: <534341B6-DE42-4C8C-BE64-4AACC2114284@opencsw.org> Hi Yahav, Am 22.02.2013 um 23:45 schrieb BIRAN, Yahav (Yahav): > In the search page http://www.opencsw.org/search/zabbix_agent/ > The following files are: > > Path > /etc/opt/csw/zabbix_agent.conf.CSW > /etc/opt/csw/zabbix_agentd.conf.CSW > /opt/csw/bin/amd64/zabbix_get > /opt/csw/bin/amd64/zabbix_sender > /opt/csw/bin/pentium_pro/zabbix_get > /opt/csw/bin/pentium_pro/zabbix_sender > /opt/csw/bin/zabbix_get > /opt/csw/bin/zabbix_sender > /opt/csw/sbin/amd64/zabbix_agent > /opt/csw/sbin/amd64/zabbix_agentd > /opt/csw/sbin/pentium_pro/zabbix_agent > /opt/csw/sbin/pentium_pro/zabbix_agentd > /opt/csw/sbin/zabbix_agent > /opt/csw/sbin/zabbix_agentd > /opt/csw/share/doc/zabbix_agent/license > /opt/csw/share/man/man1/zabbix_get.1 > /opt/csw/share/man/man1/zabbix_sender.1 > /opt/csw/share/man/man8/zabbix_agentd.8 > > But on the server after the install: > > -bash-3.2$ sudo pkgutil -y -i zabbix_agent > Solving needed dependencies ... > Solving dependency order ... > 2 CURRENT packages: > CSWcommon-1.5,REV=2010.12.11 > CSWlibiconv2-1.14,REV=2011.08.07 > Install 1 NEW packages: > CSWzabbix-agent-1.8.10,REV=2012.03.16 (opencsw/testing) > Total size: 255.2 KB > => Fetching CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... > > => Installing CSWzabbix-agent-1.8.10,REV=2012.03.16 (1/1) ... > Please see /opt/csw/share/doc/zabbix_agent/license for license information. > > Installation of was successful. > > I get the following: > > -bash-3.2$ sudo find /opt/csw/ | grep -i zabbix > /opt/csw/share/doc/zabbix_agent > /opt/csw/share/doc/zabbix_agent/license > /opt/csw/share/man/man8/zabbix_agentd.8 > /opt/csw/share/man/man1/zabbix_sender.1 > /opt/csw/share/man/man1/zabbix_get.1 > /opt/csw/bin/zabbix_get > /opt/csw/bin/zabbix_sender > /opt/csw/sbin/zabbix_agent > /opt/csw/sbin/zabbix_agentd > -bash-3.2$ sudo find /etc/ | grep -i zabbix > /etc/zabbix > /etc/zabbix/zabbix_agentd.HOST > /etc/zabbix/hostparms.HOST > /etc/zabbix/userparms > /etc/init.d/zabbix_agentd > -bash-3.2$ > > I would expect to see the /etc/opt/csw/zabbix_agent.conf.CSW > and /etc/opt/csw/zabbix_agentd.conf.CSW > > How one can view these files? You are using the wrong catalog, the listing on the webpage is always for unstable which has 2.0.0 whereas the more stable releases still have 1.8.10: -rw-r--r-- 4 web web 609497 Sep 25 23:26 beanie/sparc/5.10/zabbix_agent-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz -rw-r--r-- 4 web web 365819 Sep 25 23:24 beanie/sparc/5.10/zabbix_server-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz lrwxrwxrwx 1 web web 67 Feb 23 12:50 dublin/sparc/5.10/zabbix_agent-1.8.10,REV=2012.03.16-SunOS5.9-sparc-CSW.pkg.gz -> ../5.9/zabbix_agent-1.8.10,REV=2012.03.16-SunOS5.9-sparc-CSW.pkg.gz -rw-r--r-- 2 web web 284011 Apr 25 2012 dublin/sparc/5.10/zabbix_server-1.8.10,REV=2012.03.16-SunOS5.10-sparc-CSW.pkg.gz -rw-r--r-- 4 web web 609497 Sep 25 23:26 kiel/sparc/5.10/zabbix_agent-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz -rw-r--r-- 4 web web 365819 Sep 25 23:24 kiel/sparc/5.10/zabbix_server-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz lrwxrwxrwx 1 web web 67 Feb 23 12:50 testing/sparc/5.10/zabbix_agent-1.8.10,REV=2012.03.16-SunOS5.9-sparc-CSW.pkg.gz -> ../5.9/zabbix_agent-1.8.10,REV=2012.03.16-SunOS5.9-sparc-CSW.pkg.gz -rw-r--r-- 2 web web 284011 Apr 25 2012 testing/sparc/5.10/zabbix_server-1.8.10,REV=2012.03.16-SunOS5.10-sparc-CSW.pkg.gz -rw-r--r-- 4 web web 609497 Sep 25 23:26 unstable/sparc/5.10/zabbix_agent-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz -rw-r--r-- 4 web web 365819 Sep 25 23:24 unstable/sparc/5.10/zabbix_server-2.0.0,REV=2012.06.26-SunOS5.10-sparc-CSW.pkg.gz You can switch the catalog in pkgutil.conf, please verify with pkgutil -V Best regards -- Dago -------------- next part -------------- An HTML attachment was scrubbed... URL: From romeotheriault at opencsw.org Mon Feb 25 21:12:18 2013 From: romeotheriault at opencsw.org (Romeo Theriault) Date: Mon, 25 Feb 2013 10:12:18 -1000 Subject: [csw-users] Puppet in an OpenCSW environment In-Reply-To: References: Message-ID: On Thu, Feb 21, 2013 at 9:05 AM, Jonathan Craig wrote: > I'm interested in using puppet to begin managing our server > infrastructure and looking to the community for insight. We currently > have 450 servers (250 Solaris 10/11, 50 SUSE, 150 RedHat) to manage. > I currently manage about 140 Solaris (mostly 10) boxes and 250 RHEL boxes with Puppet. > The questions I'm grappling with are: > > 1) Puppet 2.7 vs 3.0 > I'm currently on 2.7 but if you're starting fresh I'd go with 3.x. You'll have to upgrade to it anyway at some point. While the number is a big jump there's not actually that much of a big difference between the two. (i.e. It's not like you'll be running a bunch of experimental features) > 2) Free vs Commercial > We use the free version with Foreman (http://theforeman.org/) as the frontend web ui. Been working very well. 3) OpenCSW vs GEM install > I installed the puppet deps with opencsw packages but decided to manage the puppet and facter packages via 'gem' packages. This way I don't have to deal with opencsw package upgrade dependencies as much. > 4) Should I run the master on Solaris or use RedHat with the > expectation that it will be better supported within the Puppet > community > I'd go with RHEL. You'll get better community support and I'm sure it's been more widely tested. > > So, is anyone using the puppet/puppet3 CSW module; in production? > Not sure what you mean by puppet CSW module. Do you mean pkgutil puppet package? Or the pkgutil puppet package provider? I don't use the opencsw puppet package but I'm sure it works fine. We do maintain our own local pkgutil repo and also use the pkgutil package provider. Works well. > How do you layout your directories > ? - Use CSW standards (/etc/opt/CSW, /var/opt/CSW, ...) > ? - Use standard puppet directories (/etc, /var, ...) > We use CSW standard dirs. /opt/csw and make some symlinks for puppet, facter, etc... into /usr/sbin, /usr/bin. > > Are you managing Solaris 11 Boxes? > Nope, moving off of solaris onto RHEL. > ? - What package providers do you use? > ? - pkgutil > ? - pkg > ? - sun > ?? - blastwave > ?? - sunfreeware > ? - any gotchas you know of > > How do you handle your internal packages (Business apps, admin > scripts/tools)? > ? - package them with platform specific packaging and manage with > standard providers > ? - use some other packaging and/or provider > We use a combination of packaging them into pkg packages or just pushing the scripts out. If you're starting from scratch in the configuration management area and don't have windows boxes to manage I'd recommend you take a look at Ansible (http://ansible.cc/) which is much simpler than puppet and which we're slowly moving towards (from puppet). It has good solaris support (still a few things missing for solaris) and very good RHEL support. Also worth a consideration before you choose is saltstack ( https://github.com/saltstack/salt). (I maintain the opencsw packages of it.... which I need to update to the latest version soon.) Anyway, good luck. Email directly if you want to talk more about any of this. Romeo -------------- next part -------------- An HTML attachment was scrubbed... URL: From chip at innovates.com Tue Feb 26 21:11:16 2013 From: chip at innovates.com (Schweiss, Chip) Date: Tue, 26 Feb 2013 14:11:16 -0600 Subject: [csw-users] Setting up build environment for OpenIndiana Message-ID: I'm using OpenCSW/unstable on OpenIndiana 151a7. It seems bug 5011 ( https://www.opencsw.org/mantis/bug_view_advanced_page.php?bug_id=5011) is causing python to crash. According to 'cgrzemba' building with SOS12U3 fixes this problem, so I'm attempting to setup the build environment and build the pyexpat library. What I'm trying to figure out is should I set up my build environment on OpenIndiana or Solaris 11? Cheers! -Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Wed Feb 27 09:35:42 2013 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=) Date: Wed, 27 Feb 2013 08:35:42 +0000 Subject: [csw-users] Setting up build environment for OpenIndiana In-Reply-To: References: Message-ID: 2013/2/26 Schweiss, Chip : > I'm using OpenCSW/unstable on OpenIndiana 151a7. It seems bug 5011 > (https://www.opencsw.org/mantis/bug_view_advanced_page.php?bug_id=5011) is > causing python to crash. According to 'cgrzemba' building with SOS12U3 > fixes this problem, so I'm attempting to setup the build environment and > build the pyexpat library. Cool! > What I'm trying to figure out is should I set up my build environment on > OpenIndiana or Solaris 11? Hm. Our build system was written on Solaris 10, and I'm not sure what could be potential problems on other systems. I know that Dago has put some work into running it on Solaris 11, with building IPS packages in mind. To just build Solaris 10 packages, I'd say that setting up a build environment on Solaris 10 would be the safest bet. I'm thinking what would be the requirements for a build host; the first thing that comes to mind is the basic utilities: pkgadd, pkginfo, pkgmk, pkgparam, pkgproto, pkgtrans, pkgrm. If your host can't have them, then it can't be a packaging host. Maciej