4.7 BCC Startup Flags

There are three optional flags that can be used by BCC during startup. Table 4-2 lists the flags and provides a description of each flag.

Table 4-2 Optional Startup Flags

Startup Flag

Description

d

On Linux, this flag keeps the bccd from forking (keeps the process in foreground) and log messages are printed to the running terminal screen (stdout) along with the normal syslog.

This flag is not used on NetWare.

v

On both Linux and NetWare, this flag turns on more verbose logging.

t

On both Linux and NetWare, this flag turns on tracing. With tracing turned on, certain sections of code that fail will report a message containing the condition that failed along with a file and line number in the code indicating where the condition failed. This is helpful for reporting problems to Novell Support.

4.7.1 Using BCC Startup Flags on NetWare

On NetWare, edit the sys:\system\ldbcc.ncf file and change the load bccd.nlm line to load bccd.nlm -flags. Replace flags with any combination of v and/or t. This could include v, vt, t, or tv.

4.7.2 Using BCC Startup Flags on Linux

On Linux, there are two options:

  • To use the v and t flags, edit the /etc/init.d/novell-bcc file and change the NOVELL_BCCD_ARGS= line to NOVELL_BCCD_ARGS=-flags. Replace flags with any combination of v and/or t. This could include v, vt, t, or tv.

    Do not use the d flag with this option.

  • Stop BCC by entering rcnovell-bccd stop at the server console, then restart it by entering /opt/novell/bcc/sbin/bccd -flags. Replace flags with any combination of v, t, and/or d.