env files don't need to define LOCKNAME by default
Defining LOCKNAME in your env file causes nightly to create this lock file in addition to creating a lockfile in the workspace's log directory (as defined by ATLOG).
In other words, not defining LOCKNAME still prevents multiple concurrent builds of the same workspace because of the lock file that's always present in the log directory.
Updated by Electric Monk over 6 years ago
- Status changed from New to Closed
- % Done changed from 40 to 100
commit 60a61f7adabc73a7a0cb70d200ac2a6735f4a6e8 Author: Josef 'Jeff' Sipek <email@example.com> Date: 2014-08-15T20:08:15.000Z 5092 env files don't need to define LOCKNAME by default 5091 illumos.sh env file's LOCKNAME definition is busted Reviewed by: Dan McDonald <firstname.lastname@example.org> Reviewed by: Garrett D'Amore <email@example.com> Approved by: Robert Mustacchi <firstname.lastname@example.org>