Appendix Restarting Aspera servicesWhen you change product settings, you might need to restart certain Aspera® services in order for the new values to take effect.Testing and optimizing transfer performanceTo verify that your system's FASP® transfer is reaching the target rate and can use the maximum bandwidth capacity, prepare a client to connect to an Aspera® server. For these tests, you can transfer an existing file or file set, or you can transfer uninitialized data in place of a source file, which you can delete at the destination, eliminating the need to read from or write to disk and saving disk space.Log filesThe application log file includes detailed transfer information and can be useful for review and support requests. You can configure log rotation and redirect Aspera® logging so that it is not recorded in the system log file.Preserving IBM Spectrum Scale ACLs of transferred filesAscp and Aspera Sync can preserve NFSv4 and POSIX ACLs and immutability attributes when transferring files from an IBM Spectrum® Scale (formerly GPFS) cluster to another cluster.Connecting to IBM Aspera Shares from the GUIAs of IBM Aspera Shares version 1.9.3, the client must have HSTS, HSTE, or Desktop Client installed in order to access Shares on a server with HSTS, HSTE, or Desktop Client installed.Logging client file system activity on HSTSHSTS can be configured to log operations on the server's file system that are performed from client applications (such as the HSTS in client mode, or Console).Product limitationsDescribes any limitations that currently exist for Aspera transfer server and client products.Parent topic: Desktop Client Guide for Linux