I have a default, sun supplied, apache2 install on solaris10. It's running fine, everything's great. I'm looking to add another instance, fairly happy with how to do that apart from one thing - the SMF manifest.
Can i just edit the XML file sun supplied for the default apache2 and add in details... (2 Replies)
why do inode indices starts from 1 unlike array indexes which starts from 0
its a question from "the design of unix operating system" of maurice j bach
id be glad if i get to know the answer quickly
:) (0 Replies)
brothers why inode index starts from 1 unlike array inex which starts from 0
its a question from the design of unix operating system of maurice j.bach
i need to know the answer urgently...someone help please (1 Reply)
Hi,
I need the a help can please any one give me a suggestion for Exporting the CLASS PATH in service manifest file for Solaris 10
Here i have pasted the code
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<!-- Copyright 2007 Sun... (4 Replies)
Hi..
I have an application installed in Zones and I would like to have the application started on every system reboot and stop at every shutdown.
I created start/stop/restart script in /etc/init.d and placed S and K links in rc?d directories. This works fine.
but I want to use SMF for this... (0 Replies)
Hi All,
I have a file (FileNames.txt) which contains the following data in it.
$ cat FileNames.txt
MYFILE17XXX208Sep191307.csv
MYFILE19XXX208Sep192124.csv
MYFILE20XXX208Sep192418.csv
MYFILE22XXX208Sep193234.csv
MYFILE21XXX208Sep193018.csv
MYFILE24XXX208Sep194053.csv... (5 Replies)
Discussion started by: krish_indus
5 Replies
LEARN ABOUT DEBIAN
jifty::plugin::testserverwarnings
Jifty::Plugin::TestServerWarnings(3pm) User Contributed Perl Documentation Jifty::Plugin::TestServerWarnings(3pm)NAME
Jifty::Plugin::TestServerWarnings - Stores server warnings away for later fetching
SYNOPSIS
# In your jifty config.yml under the framework section:
Plugins:
- TestServerWarnings:
clear_screen: 1
DESCRIPTION
This plugin add a new appender Jifty::Plugin::TestServerWarnings::Appender on the first request it sees, which stores away all messages it
receives. It also removes the default "Screen" appender unless clear_screen in config.yml is set to be false or env TEST_VERBOSE is true.
The warnings can be retrieved by a client-side process by calling "decoded_warnings" with a base URI to the server.
This plugin is automatically added for all jifty tests.
METHODS
init
set clear_screen to 1 if the clear_screen in config.yml is set to be true, if it's not set at all, set it to 1 if TEST_VERBOSE is set to be
true.
new_request
On the first call to new_request, the plugin adjusts the appenders. This causes it to only have effect if it is run in a forked server
process, not in a test process. If "TEST_VERBOSE" is set, it does not remove the Screen appender.
add_warnings WARN, WARN, ..
Takes the given warnings, and stores them away for later reporting.
stashed_warnings
Returns the stored warnings, as a list. This does not clear the list, unlike "encoded_warnings" or "decoded_warnings".
encoded_warnings
Returns the stored warnings, encoded using Storable. This also clears the list of stashed warnings.
decoded_warnings URI
Given the URI to a jifty server with this plugin enabled, retrieves and decodes the stored warnings, returning them. This will also clear
the server's stored list of warnings.
perl v5.14.2 2010-09-25 Jifty::Plugin::TestServerWarnings(3pm)