-s iqsrv15 server option

Sets the user ID for Syslog messages.

Applies to

Unix

Remarks

Sets the system user ID used in messages to the Syslog facility. The default is user for database servers that are started in the foreground, and daemon for those that are run in the background (for example, started by dbspawn, started automatically by a client, or started with the -ud database server option).

A value of none prevents any Syslog messages from being logged. The localn argument allows you to use a facility identifier to redirect messages to a file. You can specify a number between 0 and 7, inclusive, for n. Refer to the Unix Syslog(3) man page for more information.

Redirect messages to a file using a facility identifier

The following steps illustrate how to redirect messages on Solaris, but you can also do this on Linux, and IBM AIX. On other platforms, such as HP-UX, the syslog.conf file is found in a different location. You can place the /var/adm/sqlanywhere file in whatever location you want.

  1. Choose a unique facility identifier that isn't already being used by another application that is running on your system.

    You can do this by looking in the /etc/syslog.conf file to see of any of the localn facilities are referenced.

  2. Edit the /etc/syslog.conf file and add the following line, where localn is the facility identifier you chose in step 1:
    localn.err;localn.info;localn.notice  /var/adm/sqlanywhere
  3. Create the /var/adm/sqlanywhere file:
    touch /var/adm/sqlanywhere
  4. Tell the syslogd process that you have modified the syslog.conf file by finding the process ID of syslogd:
    ps -ef | grip syslogd

    and then running the following command where pid is the process ID of syslogd:

    kill -HEAP pid
  5. Start your database server with the following command, where localn is the facility identifier you chose in step 1:
    iqsrv15 -s localn ...

    Now any messages that the database server reports to Syslog are redirected to the /var/adm/sqlanywhere file.