Resolving problems with SRC support

Use these suggestions to resolve common problems with the System Resource Controller.

If changes to the /etc/inetd.conf file do not take effect:
Update the inetd daemon by issuing the refresh -s inetd command or the kill -1 InetdPID command.
If the startsrc -s [subsystem name] returns the following error message:
```
0513-00  The System Resource Controller is not active.
```
The System Resource Controller subsystem has not been activated. Issue the srcmstr & command to start SRC, then reissue the startsrc command.
You might also want to try starting the daemon from the command line without SRC support.
If the refresh -s [subsystem name] or lssrc -ls [subsystem name] returns the following error message:
```
[subsystem name] does not support this option.
```
The subsystem does not support the SRC option issued. Check the subsystem documentation to verify options the subsystem supports.
If the following message is displayed:
```
SRC was not found, continuing without SRC support.
```
A daemon was invoked directly from the command line instead of using the startsrc command. This is not a problem. However, SRC commands, such as stopsrc and refresh, will not manipulate a subsystem that is invoked directly.

If the inetd daemon is up and running correctly and the appropriate service seems to be correct but you still cannot connect, try running the inetd daemon processes through a debugger.

Stop the inetd daemon temporarily:
```
stopsrc -s inetd
```
The stopsrc command stops subsystems like the inetd daemon.
Edit the syslog.conf file to add a debugging line at the bottom. For example:
```
vi /etc/syslog.conf
```
1. Add the line *.debug /tmp/myfile at the bottom of the file and exit.
2. The file that you specify must exist (/tmp/myfile in this example). You can use the touch command to make your file exists.
Refresh the file:
- If you are using SRC, enter:
```
refresh -s syslogd
```
- If you are not using SRC, kill the syslogd daemon:
```
kill -1 `ps -e | grep /etc/syslogd | cut -c1-7` 
```
Start the inetd daemon backup with debugging enabled:
```
startsrc -s inetd -a "-d"
```
The -d flag enables debugging.
Try to make a connection to log errors in the /tmp/myfile debugging file. For example:
```
tn bastet
Trying...
connected to bastet
login:>
Connection closed
```
See if anything shows up as a problem in the debugging file. For example:
```
tail -f /tmp/myfile
```