Any references to / will refer to C:/Cygwin. The s option
updates the registry so all users will have the same mapping. Note
the slashes; these are the correct ones to use.
Entering the following command and pressing Enter will display all
the current mappings:
mount
The recommended approach is to choose a user record that works
properly and run the mount command to view all of its existing
mappings. Then use the unmount command to remove them. Add
them back again using the mount s command option. Otherwise,
each user will have to be updated individually.
More information is available at the following Web site:
http://www.cygwin.com/cygwin-ug-net/using.html
Troubleshooting with Logs
In general, you will be able to solve most, if not all, problems by
turning on and examining the lcfd.log and UaTk.log files. These
logs record what has gone on within the communications protocol
and the UaTk.pm Perl module.
lcfd.log
The lcfd.log file is generated by the lcfd application running on your
endpoint. You should set the logging level to 3, which is high
enough so that the protocol can be seen. The following example
shows what the protocol looks like in the lcfd.log when an
application is verified during the assignment of an endpoint
mapping.
Jun 16 12:59:11
Q tk_verify SendCommand called with eptype ora8 and command STARTUP
Jun 16 12:59:11
Q tk_verify Toolkit Protocol State: STStartup
Jun 16 12:59:12
Q tk_verify TK_Protocol Sent Message: STARTUP
Jun 16 12:59:12 Q tk_verify Toolkit Protocol State: STAck
Jun 16 12:59:12 Q tk_verify TK_Protocol Got Message:
Jun 16 12:59:12 Q tk_verify ACK
Troubleshooting
76
User Administration Version 3.8