SER 2.0 (codenamed Ottendorf) is technically quite ready for prime time. It has been extensively tested, and people report very good stability. So, you may want to start looking at it! But how to
go about it?
Good to know:
- Many important things like TCP, timers, database model etc have been done from scratch, so this is really a major release (yes, that’s why it has taken some time)
- Your old ser.cfg is not compatible
- Lots of stuff in your old ser.cfg will suddenly become much simpler
- You can migrate your old database, but start out with a clean test installation
How to get started:
- First of all, get the latest source code
- Then, unpack it and build it using make group_include=”standard” all (or use group_include=”standard mysql” if you want mysql support)
- make install will install to default /usr/local (use make prefix=/another/dir to install to another directory)
- Copy the etc/ser-basic.cfg file from the source tree to /usr/local/etc/ser/ser.cfg
- Start ser: /usr/local/sbin/ser
Congratulations, you have SER running!
- Try etc/ser.cfg for mysql support (but run scripts/mysql/ser_mysql.sh first to prepare your mysql database)
- Have a look at What’s New for an introduction to new features/changes
- The module documentation is available online
What to do if you encounter problems:
- Post a question to firstname.lastname@example.org
- If you find a bug, register it on the tracker
- If you miss something documentation, post a suggestion to email@example.com (or even better, tell what you would like to document 🙂
Jan 24, update:
I forgot to say that the old serctl tool has been replaced with a more powerful one written in python. It no longer comes as an integrated part of the SER package. I have made available a serctl download for you, if you don’t want to mess around with CVS.