Escape values in LOCKSS configuration file.
This caused a problem with the LOCKSS 2.0-alpha2 configuration, where LOCKSS_ACCESS_SUBNET used semicolons to separate values, but it should be done generally.
Loading
Please register or sign in to comment