![[Home]](http://wiki.linux-vserver.org/skins/common/images/wiki.png)
We currently migrate to MediaWiki from our old installation, but not all content has been migrated yet. Take a look at the Wiki Team page for instructions how to help or browse through our new wiki at wiki.linux-vserver.org to find the information already migrated.
Once again someone whined about the new configuration style consisting of a fantastizillion of files containing only a single value. And once again Bertl wondered why noone came up with a tool to convert back and forth between a configuration directory and a flat file... Being sick of hearing this over and over again, I hacked together two small scripts which do exactly that. [fromDir.sh] creates a .conf file for each vserver configuration directory, [toDir.sh] creates a directory for the given flat .conf file....
Adjust the path in each file to point to your configuration directory, eg. /etc/vservers
Calling fromDir.sh will then create a <vservername>.conf file for each configuration directory, the files will be in your configuration directory.
toDir.sh needs to get the flat .conf file through stdin, ie. call it like this:
toDir.sh < /path/to/vservername.conf
THIS IS NOT COMPATIBLE WITH THE OLD CONFIG STYLE .CONF FILES!
You have been yelled at^W^Wwarned!
The scripts only care about regular files, they will not delete files in your configuration directory, only create new ones or modify existing ones.
I might enhance the scripts a bit in the future, but I'd actually prefer to see some of those who complained about the directory-based config step forward and enhance or even rewrite them (I suck at bash scripting).