Dec 14, 2018
03:44 PM
1 Kudo
Summary
This article discuss why network filesystems may be excluded from inventory on UNIX-like operating systems, and how can they be included.
Question
Why are network drives excluded from inventory even when I haven't set the ExcludeDirectory preference, for example as shown in the following sample logging:
File tracking looking for files in directories '/w001/nfs'
...
File tracking of files on mount point '/w001/nfs/domains' of type 'nfs' will be excluded
I added an IncludeDirectory=/w001/nfs preference setting, and it includes and then excludes it, why is this?
Answer
The exclude comes from it being a network file system. The inventory gathering process will start its filesystem scan in the /w001/nfs directory, but it will not recurse into the sub-directory /w001/nfs/domains. This is because the default configuration is to not scan network-based filesystems.
This behavior is controlled using the following preferences: IncludeNetworkDrives (default: false) IncludeFileSystemType (default: "ufs,zfs,lofs") ExcludeFileSystemType (default: "") All of this is done to prevent the inventory gathering process from operating over a network connection. This behavior can be overridden by altering the above preferences. For example:
IncludeNetworkDrives=true IncludeFileSystemType="nfs,ufs,zfs,lofs"
For example, edit /var/opt/managesoft/etc/config.ini file under the section
[ManageSoft\Tracker\CurrentVersion]
IncludeNetworkDrives=true
This setting is affected by others like IncludeDirectory which can alter the directory to be scanned in conjunction with this setting. In order for a scan against a network drive to occur, IncludeNetworkDrives has to be set to true even if IncludeDirectory points to such a location.
For more on these preferences information, see the Preferences section in the Gathering FlexNet Inventory guide.
... View more
Labels:
Nov 13, 2018
08:35 PM
Summary Building a C# DLL Wrapper Synopsis Using FlexNet Publisher 2014 (11.13.0), how do you create a DLL that contains the licensing client library if using a C# application? Discussion Please see the "Dynamically Linking Your Application" section of the FlexNet Publisher 11.13 Development Environment Guide. The "Creating a DLL that contains the Licensing Client Library" section starts on p111. We provide an example that illustrates how to create an application in C# that uses our flexible and activation APIs; this can be found in Product and License Center under the "FlexNet Publisher Documentation, Licenses & Tools (11.13.0)" section. The specific downloads available there are: 1. Instructions for using the example C# implementation for trusted storage-based licensing 2. Example C# Implementation for Trusted Storage-based Licensing - Windows x86-64 3. Example C# Implementation for Trusted Storage-based Licensing - Windows x86-32
... View more
Latest posts by ccorpuz
Subject | Views | Posted |
---|---|---|
933 | Dec 14, 2018 03:44 PM | |
1145 | Nov 13, 2018 08:35 PM |
Activity Feed
- Posted Why are network filesystems being excluded from inventory? on FlexNet Manager Knowledge Base. Dec 14, 2018 03:44 PM
- Posted Building a C# DLL Wrapper on FlexNet Publisher Knowledge Base. Nov 13, 2018 08:35 PM