Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

240 Chapter 10
Technical Articles
Introducing Samba/iX
4. Use the following two commands to create symbolic links to make
SERVICES.NET.SYS link to /etc/services and
INETDCNF.NET.SYS links to /etc/inetd.cnf respectively:
:newlink /etc/services, /SYS/NET/SERVICES
:newlink /etc/inetd.conf, /SYS/NET/INETDCNF
5. Stream JINETD.NET.SYS or use INETD.NET.SYS -c (if INETD job
was already running) to start SMND listener and NMBD server.
6. Use SHOWOUT JOB= Jobnumber
7. Print Oxxx.OUT.HPSPOOL to check for any problems in the spool
files.
In case of problems, check for the job listings for useful error messages
and look into the Samba/iX log file /usr/local/samba/var/log.smb
and log.nmb for hints. You can control the amount of log messages
with the “debug level” directive inside the config file.
Stopping Samba/iX
It is important to shutdown Samba/iX before bringing the system down.
You can use the following commands to stop Samba/iX:
1. Use SHOWJOB to see if the jobs stay alive, it can look as follows:
JOBNUM STATE JIN JLIST JOB NAME
J#30 EXEC 10S LP JNMB,MGR.SAMBA
J#31 EXEC 10S LP JSMB,MGR.SAMBA
2. Use the following two commands to stop Samba/iX:
:abortjob #smbjobnumber
:abortjob #nmbjobnumber
Logging Method
The Samba/iX programs write trace messages into a log file called
log.smb or log.nmb by default. The log files reside in
/usr/local/samba/var directory.
The level of detail is controlled by a "debug level" option in the Samba
configuration file which is smb.conf file. The debug level is an integer
from 0 to 5. The high this value is, the more detail will be logged to the
log file about the activities of the server. At level 0, only critical errors
and serious warnings will be logged. Level 1 generates a small amount
of information about operations. Level above 1 will generate
considerable amount of trace messages which can be used for trouble
shooting problems.