-
There are now RPM's for php-propel at PLD's download sites. I've tweaked them for RHEL, and will try to get them into RPMforge.
The dependencies are:
php-pear-creole (available from Fedora 9 SRPM)
php-channel-phpdb (available from Fedora 9 SRPM)
minor rewrites of the php-propel.spec file, preferably renaming it php-pear-propel.spec and updating to propel-1.3.0RC1.
2008-06-20 00:22:53 UTC in The Lilac Network Configuration Platform
-
And oh, yes, in case you didn't, know, Fruity is dead. It's been forked and renamed, to 'Lilac', and development is proceeding over at http://sourceforge.net/projects/lilac/.
2008-04-27 12:44:08 UTC in Fruity : A Nagios Configuration Tool
-
Tobias, this was an issue in Fruity, too.
sudo actually has some problems in recent configurations, such as RHEL 5, where it won't run these commands without a tty. This disables it running from Apache. And the Nagios reload command is, historically, not reliable when the configurations have changed a lot: I never succeeded in tracking down what it tripped over, but it's not reliable...
2008-04-27 12:41:59 UTC in Fruity : A Nagios Configuration Tool
-
The list of dialrules is quite small. Please add those from http://lahtermaher.org/pub/packages/hylafax/contrib/dialrules/, especially the rather antique dialrules.ext for handling extensions and locations that require a leading "9," to dial out. In fact, if you look for dialrules.ext and HylaFAX on Google, you'll mostly find me publishing it or pointing it out to people.
It would also be...
2008-02-08 12:32:21 UTC in HylaFAX
-
Hmm. Restoring previous MySQL dumps would be useful indeed. I'd want to be cautious about accumulating dumps every time you export the configuration, lest you seriously clutter wherever you're working while you're making big sets of changes. But keeping the last one or two could *certainly* be a lifesaver.
A tool to translate the fruity/Lilac dumps directly into a set of Nagios config setups...
2007-12-15 09:22:42 UTC in The Lilac Network Configuration Platform
-
You couldn't issue a query for services pointing to the old hostgroup and delete them appropriately when you delete the hostgroup? Even modifying the "Services" display page to list services not associated with specific hosts or hostgroups would allow GUI access to these dangling services, and allow flushing them manually. As it is, you have to go into the MySQL directly to clear them. (I use...
2007-12-15 09:18:34 UTC in The Lilac Network Configuration Platform
-
I didn't write the original bug report on that one, I just ported it from the Fruity bugs because it looks fairly nasty. There have consistently been a set of import and export inconsistencies, where doing an import and a re-export reproduces fundamentally different configurations. I'm afraid to say that I don't have a running Nagios/Lilac/Fruity setup right now, since I just started a new...
2007-12-15 09:14:25 UTC in The Lilac Network Configuration Platform
-
An extended entry with no content is "empty". You may always use extended entries for your systems and thus not see this, but I generally don't. The result is a lot of configuration clutter of information I didn't publish and don't need, and it clutters "import" operations as well.
It's not a deadly bug, merely irksome.
2007-12-15 09:03:22 UTC in The Lilac Network Configuration Platform
-
[Copied from Fruity bug 167674.]
Comparing the contents of an old, backed up, previously working Nagios configuration with the new one from Fruity is very awkward. It would be much easier to simply use a backup directory: flush it before the export operation, move the old config there, and then create the new files.
2007-12-12 12:00:00 UTC in The Lilac Network Configuration Platform
-
[Ported from bug 1679294 in Fruity]
Storing blank entries simply wastes space and makes configurations harder to port to non-Fruity based setups, and vice versa, especially when the information is originally imported without any such data.
I'm not a PHP expert, cut a check to sum up the various fields and skip printing the host entry if it's empty should be straightforward.
2007-12-12 11:57:50 UTC in The Lilac Network Configuration Platform
