Installing Services

After services have been installed, in this manner, you should be able to start them by running the binary. If the IRC server is running and both services and your IRC server are properly configured, services will then activate. However, if you have been installing services using administrative access on your machine, stop now , make a separate services account, and ensure that the databases and database directories where the logfiles will be written are all owned by that account. Never run services as root for any reason.

To gain administrative access within services during the first services session, start services, register your nickname with NickServ, add a line that reads 'SRA:nickname_here' to your services.conf file, and finally, restart services. Once you have administrative access, new configuration options can be added and helpfiles can be updated with the /OperServ reset command.

Once services start, and you are able to interact with services, the installation is completed. It is, however, a good idea to test services functions that required special actions on your part to work properly: Test to ensure that requests such as /NickServ HELP work (if it fails, you may not have installed the helpfiles properly, see the section called “Installing Services”.), and register sample nicks, channels, memos, triggers, and restart services to ensure all databases are being written: if they are not, ensure that the permissions on the files and directories allow the services user full access to those files.

If services fail to start, core.log, and notices sent to +s users on the IRC server you were trying to connect services to are good places to start looking for information on why the startup failed.