10-24-2008 11:00 AM
The essence of the FreeNAS server is to provide storage that is easily accessible from the network. To this end, it is important to understand how FreeNAS handles hard disks and how they can be configured and used to provide the best and most reliable storage for your network.
i have installed freeNAS in one vmware machine and same way i have an solaris vwmare setup. i have created a volume about 500mb using freeNAS. but after that i blacked out.
1. How shall i make solaris access this share?
2. What all configuration i have to make from solaris end.
NOTE: my... (18 Replies)
Poet::Manual::Configuring(3pm) User Contributed Perl Documentation Poet::Manual::Configuring(3pm)NAME
Poet::Manual::Configuring - Built-in Poet configuration options
DESCRIPTION
This is a list of configuration keys used by Poet itself. These may be placed in any Poet conf file, e.g. "local.cfg" or
"conf/global/*.cfg".
Entries like "foo.bar" can be listed either in dot notation
foo.bar: 5
or as part of a hash:
foo:
bar: 5
See Dot notation for details.
cache
The entire hash under this entry will be passed to Poet::Cache->config(). See Poet::Cache for examples. e.g.
cache:
defaults:
expires_variance: 0.2
storage:
file:
driver: File
root_dir: ${root}/data/cache
memcached:
driver: Memcached
servers: ["10.0.0.15:11211", "10.0.0.15:11212"]
compress_threshold: 4096
namespace:
/some/component: { storage: file, expires_in: 5min }
/some/other/component: { storage: memcached, expires_in: 1h }
Some::Library: { storage: memcached, expires_in: 10min }
env.bin_dir, env.comps_dir, etc.
These entries affect what is returned from "$poet->bin_dir", "$poet->bin_path", "$poet->comps_dir", etc., and thus where various Poet
resources are kept. See Poet::Environment. For example, to move data and logs into external directories outside the environment:
env:
data_dir: /some/external/data/dir
logs_dir: /some/external/logs/dir
log.defaults, log.category
Specify the log level, output location, and layout string for logging, in the default case and for particular categories respectively.
See Poet::Log for examples. e.g.
log:
defaults:
level: info
output: poet.log
layout: "%d{dd/MMM/yyyy:HH:mm:ss.SS} [%p] %c - %m - %F:%L - %P%n"
category:
CHI:
level: debug
output: chi.log
layout: "%d{dd/MMM/yyyy:HH:mm:ss.SS} %m - %P%n"
MyApp::Foo:
output: stdout
log.log4perl_conf
Bypass Poet's simplified logging configuration and specify a log4perl conf file directly. e.g.
log:
log4perl_conf: /path/to/log4perl.conf
mason
The hash under this entry will be treated as options that are passed to "Mason->new" for the main Mason instance, overriding any
default options. See Poet::Mason. e.g.
mason:
static_source: 1
static_source_touch_file: ${root}/data/purge.dat
server.default_content_type
Content type for requests that don't explicitly set one. Defaults to "text/html".
server.host
The IP address to listen on.
server.load_modules
A list of modules to load on server startup, e.g.
server.load_modules:
- DBI
- List::Util
- MyApp::Foo
- MyApp::Bar
server.port
The port to listen on.
SEE ALSO
Poet
AUTHOR
Jonathan Swartz <swartz@pobox.com>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Jonathan Swartz.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-06-05 Poet::Manual::Configuring(3pm)