Fixed issue with the Razor daemon ignoring the node_expire_timeout value.
Modified the Razor daemon so that it uses the new (not sure how new)
syntax added recently to separate out slices that provide a "JSON interface"
from those that provide a "Web interface".  It turns out that invoking a
"razor -w config" command now returns an "InvalidSlice" error rather than
returning the current configuration for the Razor server...the new syntax
that must be used to obtain the configuration is "razor -j config" (and this
change in syntax had not been propagated out to everywhere that we were
using the older "razor -w config" command, including the razor_daemon.rb
script where the result was that the node_expire_timeout value contained in
the Razor configuration was being ignored and a default (15 minute) value
for this node_expire_timeout parameter was being used instead.
Merge pull request #406 from tjmcs/tb/fix_razor_config_slice_error

Fixes #405 (Razor daemon ignoring the node_expire_timeout value)