We are running Sharity v2.7 on a Sunblade 2000 (Solaris 8). The problem
encountered is not one of functionality; Sharity does mount the requested smb
shares of several Windows machines, some running NT 4.0 sp6 and others XP Pro.
The issue arises when the mounted shares are accessed, either through the file
manager or the console (note that the GUI has not been started). Accessing the
/CIFS mount produces the following message:
Jul 19 16:27:10 apollo sharity[1438]: [1] sysNetworkInterfaces: ioctl(, SIOCGIFFLAGS): [6] No such device or address Jul 19 16:27:10 apollo sharity[1438]: [1] sysNetworkInterfaces: ioctl(, SIOCGIFFLAGS): [6] No such device or address
Where Apollo is the name of the Solaris server. While we are running the file
manager this message is repeated every 30 seconds as long as we remain in the
CIFS directory. If we are using the console, the message is printed as soon as
the ls command is given.
This is a bug in the current Sharity code. Fortunately, the log message is the only effect of this bug. You can work around it by explicitly telling Sharity about your network configuration. In the file /usr/local/sharity/etc/sharity.cfg search for the line
// networkInterfaces = ("192.168.1.21/24", "192.168.2.23/24");
remove the remark sign at the start of the line and change the IP address (and netmask specification) to match your system. The example given above is for two network interfaces.
If we enter a sub-directory (using file manager) for
one of the Windows machines, the above message is produced with the same
frequency, however for some machines the following additional line is written
before the lines above:
Jul 19 17:08:26 apollo sharity[1438]: [1] cifsbrowse: serverEnum result incomplete
This means that there are MANY Windows machines in your domain or workgroup. The CIFS specification does not allow messages of such a size and the Windows server which provides the list simply discards some computer names. Sharity warns you because the computer you want to access may have been discarded and therefore not be listed in the CIFS directory.
When accessing the file through a console the messages occur when the command
"cd /CIFS/<computer name>" is given and subsequently when the ls command is
given. I will reiterate that this is not a problem of functionality, we can see
and access all shares on our machines, but would like to know whether these
system messages are to be expected.
Regards, Christian.
-- Dipl.-Ing. Christian Starkjohann Objective Development mailto:[EMAIL PROTECTED] | http://www.obdev.at/
_______________________________________________ Sharity-talk mailing list [EMAIL PROTECTED] To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk
