Chat now with support
Chat with Support

DR Series Software 4.0 - Release Notes

Known issues and resolutions

Known issues and resolutions

The following table lists known issues and related resolutions addressed in this DR Series system release.

ID

Issue

Resolution

31243

Error on DR4000 after upgrade when backing up to 1.0 data store.

Resolved in this 4.0.0278.0a release. This issue only impacted a DR4000 that still contains release 1.0 backup data.

31059

Loop in self-healing routine in specific failure scenario.

Resolved in this 4.0.0278.0a release.

31017

Replication error upon bringing system into maintenance mode when using older data format from a 2.x release.

Resolved in this 4.0.0278.0a release.

30375

New Quest DLV license support.

This feature has been added in version 4.0 to support Quest and Dell license formats.

29936

Domain users that are not in login group can still log on.

This issue has been addressed in version 4.0.

29769

BE 2015 NOT able to detect NDMP VTL devices mapped to NetApp C Mode filerwhen NetApp filer is configured in vserver scope mode.

Configure NetApp for 7 Mode or for NetApp C Mode for node scope mode and Node IP used is NDMP host to BE server.

29704

File system crash.

This has been addressed in version 4.0.

29696

Creating any new username containing "administrator" substring as leading characters in the username and CIFS role causes administrator login via the GUI to be locked out.

This issue has been addressed in version 4.0.

29672

DR4300e maxing out at 4 million files on some configurations.

This issue has been addressed in version 4.0. The DR4300e now supports 64 million files.

29576, 25733

Replication failure under some rare corner cases.

This issue has been addressed in version 4.0.

28862

Time-out during seed copy to some slower USB devices.

Contact Technical Support to help you reduce the seeding threads so that the DR Series system does not overwhelm the client and USB device.

28561

Hyper-V client unable to discover VTL on higher-mapped LUN.

You must have a LUN 0-7 mapped to discover high-mapped LUN numbers. This is a Hyper-V issue.

28287

Unable to seed 3.x data to a 4.x system.

If you gathered a seed in 3.x you must finish your seed operation before upgrading to version 4.0.

28187

Setting a replication relationship with a target container has poor savings compared to the source.

If you create a replication relationship with a target container that already exists make sure the marker type is set to the correct type to match the source container.

27735, 27727

Deletion of replication pair with millions of files can take a very long time on target. This can also occur when reestablishing a relationship between a source and target container with a very large number of files.

Make sure replication is in sync before deleting the replication pair, or turn off replication before deleting the relationship. This will reduce the amount of unnecessary housekeeping needed if you are planning to delete the replication target.

27175

Upgrading from 1.x or 2.x to 4.0 is not prevented.

Your system should have 3.x before upgrading to 4.0. See the upgrade section at the beginning of these release notes.

26137

Under some conditions seeding job does not get removed from DR Series system when job is removed via CLI.

This issue has been addressed in version 4.0.

25105

Unable to change the IP from Static to DHCP if using the same IP address.

You must first enter a temporary IP address with a different number and then change to the IP you wish to use.

23767,21084

Disconnect under heavy load with Veeam, SQL, and other CIFS workflows.

This issue has been addressed in version 4.0.

21715, 24242

Cleaner improvements in laundry processing size.

This issue has been addressed in the 3.2.0.2 maintenance release as well as version 4.0.

21496

On a DR2000v with ESX 5.5, web pages, pinging operations, etc. are timing out using TLB bonding.

Disable the second bond to work around this issue.

17216

The DR Series system is not Beast/Crime-vulnerable out of the box.

To keep this security intact, you should run one of the modern browsers that supports TLS 1.2 or greater.

16280

When you try to get replication statistics, the system displays the Software error: Use of uninitialized value in division (/) at helper.pl line 3548 error.

This issue has been addressed in version 4.0.

Parent topic 

Resolutions for earlier releases

Resolutions for earlier releases

The following table lists known issues, descriptions, and related solutions or workarounds for the previous DR Series system releases.

ID

Issue

Workaround/Solution

30465

New Quest DLV license support.

This feature was added in release 3.2.6.2 and 3.2.0.3 to support Quest and Dell license formats.

29733

Incorrect output was displayed when using the command cleaner --show_log_files.

This issue was addressed in release 3.2.6.2 and 3.2.0.3.

29618

Login issue with login groups.

This issue was addressed in release 3.2.6.2 and 3.2.0.3.

29540

Incorrect stats included in daily report for replication target.

This issue was addressed in release 3.2.6.2 and 3.2.0.3.

29421

Need to increase RPC client timeout for node start/stop.

This issue was addressed in release 3.2.6.2 and 3.2.0.3.

29266

Need to add cleaner tunable parameter for laundry size.

This feature was added to release 3.2.6.2 and 3.2.0.3. Note that this parameter must be tuned by Technical Support.

28499

Add cleaner GUI usage graph for cleaner details.

This feature was added to release 3.2.6.2 and 3.2.0.3.

28484

DR4300 systems displayed incorrect drive sizes/capacity for 4TB drives when using RM factor reset.

This was fixed in the release 3.2.6.1 RM package.

27625, 27555

Replication was encountering system crashes in some rare cases.

This was fixed in release 3.2.6.1.

26721

NDMP VTL device appears offline.

This was fixed in release 3.2.6.1.

26685, 25675

ocafsd was crashing on cleaner code in some rare instances.

This was fixed in release 3.2.6.1.

25908

NDMP restore fails when backup is restarted with CommVault Simpana with large amounts of data.

This was fixed in release 3.2.6.1, and NDMP Backup Restartable Extensions (BRE) are now supported.

28032

The DR4000 crashes when breaking a replication relationship and running fsck.

This issue was addressed in 3.2.0.2.

27847

RDNFS plugin issue with Oracle Linux 7.0.

This issue was addressed in 3.2.0.2.

27736, 27671

Replication fix for large configurations.

This issue was addressed in 3.2.0.2.

26191

System cleaner timeout fix.

This issue was addressed in 3.2.0.2.

28439

After updating to release 3.2.0.1, the fan speed was 8K but should be 10K by default.

This was fixed in release 3.2.0.2.

23879

Backup spanning across multiple tapes fail when 10 GB tape is used for Microsoft DPM.

Recommendations for backups spanning multiple tapes are documented in the DR Series best practices guide for Microsoft DPM available for your specific DR Series system at dell.com/support/home.

23641

Cannot join into the domain by adding a DR Series system to multiple OUs.

In the authenticate command type the format as follows:--ou topLevelOU/middleLevelOU/LowerLevelOU/TargetOU  This format for adding OUs is now documented in the latest Dell DR Series System CLI Guide.

This was addressed and documented in release 3.2.6.

20870

RPC replication errors may be seen during replication from source DR Series system to target DR Series system. The primary and secondary replication target should have the same MTU setting. Replication proceeds once the MTU is set to the same as the replica target. This recommendation has been added to the section, “Managing Replication Operations,” in the latest Dell DR Series System Administrator’s Guide.

This was addressed and documented in release 3.2.6.

20539

After installing Rapid CIFS Filter Driver, an incorrect driver version is displayed.

Addressed and documented in release 3.2.6.

If at the end of successful installation, the version of the driver loaded (which can be checked using rdcifsctl.exe driver -q) is lower than the version of the installed package (listed under Control Panel > Installed products), then you should restart the machine. This issue can occur if the system fails to rename/delete driver files under the system folder.

20456

Installation of SSL Certificate file in the GUI failed on Internet Explorer (IE) when using Remote Desktop.

Addressed and documented in release 3.2.6.

When uploading the certificate file, the GUI uses the file name with the whole path, which works when uploading on a local system. When using RDP, in the IE browser settings, you need to disable the "Include local directory path .." setting, as follows.

1.
Under Internet Options > Security, in the "Internet" or "Intranet" area, click Custom Level.
2.
In the Security settings, scroll down to Include local directory path when uploading files to a server and ensure it is not selected.
3.
Click OK and the refresh the browser.

20424

The following message may appear on the console: “vx_nospace...” even if the system still has space.

Addressed and documented in release 3.2.6.

This message is a result of trying to allocate a large contiguous block. The allocation of the contiguous block might fail, in which case, allocation continues without trying to keep the file contiguous. The vx_nospace error may appear, and this message can be safely ignored.

20188

When using cascaded replication for a large number of files (1M+), it may appear to take some time to see the actual files on the secondary target.

Addressed and documented in release 3.2.6. Namespace resync has to complete on the source and primary target and then data transfer has to start on both before transferring to the secondary target. Once the namespace resync completes on the first replication pair, resync then starts on the second replication pair. Until the namespace resync completes on the second pair, no data is transferred. This ensures the namespace resync completes faster and the snapshot can be deleted faster.

20009

User is able to create/write a file/directory in the share/container even though the user has only read permissions (file-level/security-level) on the share.

Addressed and documented in release 3.2.6. You can block write/create operations for a particular domain user by adding an extra ‘Deny’ ‘write’ acl for that user. (This issue occurs on the Windows 2008 client.)

19884

RDA plugin logging is not generated by default on physical hosts protected by vRanger because the plugin log service delldrlogsvc.exe is not installed by default.

Addressed and documented in release 3.2.6. To enable RDA plugin logging on physical hosts:

1.
Copy %INSTALLDIR\Dell\RDA\dynlib\delldrlogsvc.exe from the vRanger server to the %INSTALLDIR\Dell\vRangerPhysicalClient\<timestamp>rofs directory on the physical host.
2.
Change the directory to: %INSTALLDIR\Dell\vRangerPhysicalClient\<timestamp>rofs
3.
Run the command: delldrlogsvc.exe install
4.
Run the command: delldrlogsvc.exe start

19552

When there is no data to replicate (for example, replication state is INSYNC), replication statistics might indicate a target is running out of disk space even though the target has enough space.

Addressed and documented in release 3.2.6. This occurs because the replication process detected target space full condition when there is pending data to be replicated, but, at a later time, that pending data was removed and replication was insync. We do not query target disk state when replication is idle. On a similar note, we might not indicate target space full condition when there is no data to replicate as well. An error state in the replication statistics makes sense only when replication is not in sync.

19485

Adding a host name does not work if you use a FQDN and the host name has letters in it.

Addressed and documented in release 3.2.6. You can add names as long as the name is made only of numbers and it is not a FQDN where a period is used in the name string.

19186

If you change the hostname or the domain name after setting up the DR Rapid plug-in, then you may get the wrong backup mode pass-through or de-dupe.

Addressed and documented in release 3.2.6. Uninstall and then reinstall the DR Rapid plug-in for this information to be set correctly.

19023

Events information is not captured in the GUI when the date and time under System Configuration is changed to a date and time in the past.

Addressed and documented in release 3.2.6. This type of event information is captured in the CLI, by using the –show –alerts|more command.

18848

In the Internet Explorer 9 and 10 browsers, when you navigate to a DR Series system from within Global View, and then log out of that system and return to Global View, you are logged out of the machine running the Global View.

Addressed and documented in release 3.2.6. This issue does not occur with any other supported browser. For browser information, see the Dell DR Series System Interoperability Guide.

18178

The AIO-Stress tool fails when using Rapid NFS.

Addressed and documented in release 3.2.6. Rapid NFS, which uses FUSE, does not support AIO.

18501

Rapid NFS performance drops significantly with parallel NFS ingest from same client.

Addressed and documented in release 3.2.6. When using Rapid NFS on your client, it is suggested that you do not run NFS from the same client to the DR Series system in parallel as this will affect your overall performance.

18144

A File name too long error is displayed after trying to create a directory structure that exceeded 522 directories.

Addressed and documented in release 3.2.6. The limit on a path within a mount point is 4096 bytes.

18022

Windows 2008 and newer servers cannot assign local users (other than administrator) to Access Control Lists (ACLs). Windows 2008 and later does not query the local users on the DR Series platform.

Addressed and documented in release 3.2.6. Assign ACLs to the built-in Administrator user on the DR Series platform if using Windows 2008 and later.

17661

If the cable is removed from a network interface and the network is restarted, the interface does not get an IP. If you then reinsert the cable, you must restart the network to get an IP.

Addressed and documented in release 3.2.6. Ensure that the interfaces that you want to add or modify are connected when making Advanced Networking changes. To restart the network, type network --restart at the CLI command line.

17193

DR Rapid critical message Alert RDS Restore failed reported on DR4x00 system. In addition to the error, an event is generated internally in the DR Rapid plug-in when the read operation fails

Addressed and documented in release 3.2.6. The DR Rapid plug-in generates events for any kind of read failures.

16745, 17621

If you have the same client for OST and RDS operations and you manually update the client connections, unexpected messages are displayed as: [root@swsys-49 ~]# stats -- clients --type RDA RDA Client(s) Type plug-in OS Backup Software Last Access Connection(s) Mode r310-sys-39 RDS -- -- -- -- 0 Default

[root@swsys-49 ~]# ost -- update_client --name r310- sys-39 --mode auto Client is connected with default values. Please update to non-default values.

In Linux systems, the RDS plug-in installation fails if the OST plug-in is already installed in the system

Addressed and documented in release 3.2.6. To work around the issue, use a different client for OST and RDS rather than sharing the same machine for both protocols.

16660

When BE has an issue connecting to the server, it may not return detailed errors to the OST plug-in.

Addressed and documented in release 3.2.6. See the client log files for the detailed information on the connection failure.

16427

When upgrading your system using the iDRAC, if the upgrade package also contains new iDRAC firmware, the upgrade fails to complete.

Addressed and documented in release 3.2.6. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC.

16053

After you install the Rapid CIFS plugin and replication operations are performed, you receive a blue screen and the following error: STOP 0x00000027 (parameter1, parameter2, parameter3, parameter4) RDR_FILE_SYSTEM

Addressed and documented in release 3.2.6. This is a Microsoft bug that occurs on shared network resources on a computer that is running Windows Server 2008 R2 or Windows 7. To fix, see the Microsoft KB2584874.

9433

The dedicated hot spare is not automatically configured after replacing the hot spare drive in slot 0.

Addressed and documented in release 3.2.6. If the hot spare is replaced, run maintenance by using the --make_standby command. Contact Dell Technical Support for this action.

27074

iSCSI VTL configuration with IBM Tivoli Storage Manager 7.1.1 fails at audit tape library.

Corrected in release 3.2.0.1.

27074

Symantec Backup Exec inventory issue.

Corrected in release 3.2.0.1.

27013

Issue with an ofsck refcount record boundary calculation.

Corrected in release 3.2.0.1.

26721

NDMP VTL device offline issue.

Corrected in release 3.2.0.1.

26548

Kernel panic fix for VTL running in parallel with other protocol heavy replication.

Addressed in release 3.2.0.1.

26493

Option added to increase RDA retry capability in registry working with Tech Support.

Addressed in release 3.2.0.1.

26282

Support for RDA for Sparc.

Addressed in release 3.2.0.1.

26265

DR plugin DellDRLogSvc service does not always stop when uninstalling NetVault.

Corrected in release 3.2.0.1.

26190

Various VTL updates for release 3.2.6 ported to 3.2.0.1 code.

Addressed in release 3.2.0.1.

26128

RFE: OFSCK: re-organized refcnt record structure to optimize disk space.

Addressed in release 3.2.0.1.

26113

NFS fix for moujnt during stats call.

Corrected in release 3.2.0.1.

25958

Veeam ingest and replication issue for large file overwrite corner case.

Corrected in release 3.2.0.1.

25860

NetVault Backup stats file takes a long time in closing.

Corrected in release 3.2.0.1.

25675

ocafsd crashed on cleaner code due to corner case.

Corrected in release 3.2.0.1.

25591

Space handling improvements related to global space thresholds and per enclosure thresholds for Rapid NFS and Rapid CIFS.

Addressed in release 3.2.0.1.

25584

Improved seeding for CIFS on slow networks

Addressed in release 3.2.0.1.

25393

Cleaner is now set to run during idle time even when not in schedule. Since the machine is idle cleaning will occur; it will be stopped if I/O is started.

Addressed in release 3.2.0.1.

25135

Let cleaner finish if it is in runonce mode even if there is a cleaner schedule stop.

Addressed in release 3.2.0.1.

25091

cifs_iobuf_alloc fix for iSCSI.

Addressed in release 3.2.0.1.

24998

Fixed complex replication deadlock scenario involving overwrites and aborts.

Addressed in release 3.2.0.1.

24855

VTL subsystem starts if container name contains "ISCSI" or "NDMP" even though the container type is not 'vtl'.

Corrected in release 3.2.0.1.

24809

Corner case fix for cascaded replication.

Addressed in release 3.2.0.1.

24738

Validate the timestamps in mds supplied by user.

Addressed in release 3.2.0.1.

24701

DR VTL was showing support for hardware encryption, which is not accurate. Removed this option as Symantec was allowing encryption setting. (SPIN, SPOUT and publishing in MODE SENSE)

Corrected in release 3.2.0.1.

24689

Some of the documentation PDF links were not working in the DR Series system GUI.

Corrected in release 3.2.0.1.

24579

Unable to log in using domain user starting with letter "j".

Corrected in release 3.2.0.1.

24571

Enclosure showing as “Not Configured” when another enclosure is added, which changed ID numbers.

Corrected in release 3.2.0.1.

23887

Corner case where cleaner schedule will not stop cleaner from running, nor does the cleaner stop command.

Corrected in release 3.2.0.1.

23797

NDMP user name must be changed to ndmp_user in GUI.

Addressed in release 3.2.0.1.

24312

Certain hypervisor host NICs will perform poorly and may require a driver update to fully support VMQ feature.

Note that this works as designed. To resolve this issue you should check on your Hypervisor host NIC feature list and update the driver to the latest version.

For example, Broadcom NetXtreme I and NetXtreme II Ethernet adapter needs to get driver update to 17.6.0 or above to add VMQ support, otherwise you may experience performance degradation during normal operations.

Driver for NetXtreme I and NetXtreme II Ethernet adapter: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=CYKKJ&osCode=MWS80&fileId=3197327398&languageCode=EN&categoryId=NI

Firmware for NetXtreme I and NetXtreme II Ethernet adapter: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=P32M4&osCode=MWS80&fileId=3197328666&languageCode=EN&categoryId=NI

20539

After installing Rapid CIFS Filter Driver, an incorrect driver version is displayed.

If at the end of successful installation, the version of the driver loaded (which can be checked using rdcifsctl.exe driver -q) is lower than the version of the installed package (listed under Control Panel > Installed products), then you should restart the machine. This issue can occur if the system fails to rename/delete driver files under the system folder.

20456

Installation of SSL Certificate file in the GUI failed on Internet Explorer (IE) when using Remote Desktop.

When uploading the certificate file, the GUI uses the file name with the whole path, which works when uploading on a local system. When using RDP, in the IE browser settings, you need to disable the "Include local directory path .." setting, as follows.

1.
Under Internet Options > Security, in the "Internet" or "Intranet" area, click Custom Level.
2.
In the Security settings, scroll down to Include local directory path when uploading files to a server and ensure it is not selected.
3.
Click OK and the refresh the browser.

20424

The following message may appear on the console: “vx_nospace...” even if the system still has space.

This message is a result of trying to allocate a large contiguous block. The allocation of the contiguous block might fail, in which case, allocation continues without trying to keep the file contiguous. The vx_nospace error may appear, and this message can be safely ignored.

20009

User is able to create/write a file/directory in the share/container even though the user has only read permissions (file-level/security-level) on the share.

You can block write/create operations for a particular domain user by adding an extra ‘Deny’ ‘write’ acl for that user. (This issue occurs on the Windows 2008 client.)

19485

Adding a host name does not work if you use a FQDN and the host name has letters in it.

You can add names as long as the name is made only of numbers and it is not a FQDN where a period is used in the name string.

19186

If you change the hostname or the domain name after setting up the DR Rapid plug-in, then you may get the wrong backup mode pass-through or de-dupe.

Uninstall and then reinstall the DR Rapid plug-in for this information to be set correctly.

18848

In the Internet Explorer 9 and 10 browsers, when you navigate to a DR Series system from within Global View, and then log out of that system and return to Global View, you are logged out of the machine running the Global View.

This issue does not occur with any other supported browser. For browser information, see the Dell DR Series System Interoperability Guide.

18178

The AIO-Stress tool fails when using Rapid NFS.

Rapid NFS, which uses FUSE, does not support AIO.

18501

Rapid NFS performance drops significantly with parallel NFS ingest from same client.

When using Rapid NFS on your client, it is suggested that you do not run NFS from the same client to the DR Series system in parallel as this will affect your overall performance.

18144

A File name too long error is displayed after trying to create a directory structure that exceeded 522 directories.

The limit on a path within a mount point is 4096 bytes.

18022

Windows 2008 and newer servers cannot assign local users (other than administrator) to Access Control Lists (ACLs). Windows 2008 and later does not query the local users on the DR Series platform.

Assign ACLs to the built-in Administrator user on the DR Series platform if using Windows 2008 and later.

17661

If the cable is removed from a network interface and the network is restarted, the interface does not get an IP. If you then reinsert the cable, you must restart the network to get an IP.

Ensure that the interfaces that you want to add or modify are connected when making Advanced Networking changes. To restart the network, type network --restart at the CLI command line.

17193

DR Rapid critical message Alert RDS Restore failed reported on DR4x00 system. In addition to the error, an event is generated internally in the DR Rapid plug-in when the read operation fails

The DR Rapid plug-in generates events for any kind of read failures.

16745, 17621

If you have the same client for OST and RDS operations and you manually update the client connections, unexpected messages are displayed as: [root@swsys-49 ~]# stats -- clients --type RDA RDA Client(s) Type plug-in OS Backup Software Last Access Connection(s) Mode r310-sys-39 RDS -- -- -- -- 0 Default

[root@swsys-49 ~]# ost -- update_client --name r310- sys-39 --mode auto Client is connected with default values. Please update to non-default values.

In Linux systems, the RDS plug-in installation fails if the OST plug-in is already installed in the system

To work around the issue, use a different client for OST and RDS rather than sharing the same machine for both protocols.

16660

When BE has an issue connecting to the server, it may not return detailed errors to the OST plug-in.

See the client log files for the detailed information on the connection failure.

16427

When upgrading your system using the iDRAC, if the upgrade package also contains new iDRAC firmware, the upgrade fails to complete.

Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC.

9433

Global hot spare is not automatically configured after replacing the GHS drive in slot 0.

If the global hot spare is replaced, run maintenance by using the --make_standby command to make the drive a global hot spare. Contact Dell Technical Support for this action.

Parent topic 

Third Party Components

Third Party Components

GPL (GNU General Public License) 2.0
GNU (General Public License) 3.0
GNU (Lesser General Public License) 3.0
Open SSL License
The MIT License (MIT)
Copyright Notices

This product contains the third-party components listed below.

Source code for some components can be found at http://opensource.dell.com.

Copyright notices can be found below at Copyright Notices .

Component

License

Notes

keyutils utility 1.2.1.el5

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GNU (Lesser General Public License) 3.0

libtalloc2 2.0.8.24.1

GPL (GNU General Public License) 3.0

A copy of the license can be found below at GNU (Lesser General Public License) 3.0

libsigc++20 2.2.4.2.1.el6

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GNU (Lesser General Public License) 3.0

libxml++ 2.30.0.1.el6

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

Linux SCSI target framework

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

mhVTL

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

OpenSSL 1.0.1e

OpenSSL License

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

A copy of the license can be found below at Open SSL License

Samba 3.5

GPL (GNU General Public License) 3.0

A copy of the license can be found below at GNU (General Public License) 3.0

Xmlsec1 2.12.8.el6

MIT

A copy of the license can be found below at The MIT License (MIT)

xmlsec1-openssl 2.12.8.el6

OpenSSL License

A copy of the license can be found below at Open SSL License

 
 

GPL (GNU General Public License) 2.0

GPL (GNU General Public License) 2.0

GNU GENERAL PUBLIC LICENSE VERSION 2

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1.
You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2.
You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a.
You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b.
You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c.
If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3.
You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a.
Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b.
Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c.
Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4.
You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5.
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6.
Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7.
If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8.
If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9.
The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10.
If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11.
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

[one line to give the program's name and a brief idea of what it does.] Copyright (C) [year] [name of author]

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author

Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.

This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.

[signature of Ty Coon], 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

Parent topic 
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating