Bug 28249 - flexlm cant query dongle in parrallelport
flexlm cant query dongle in parrallelport
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-18 22:03 EST by Need Real Name
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-19 07:06:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-02-18 22:03:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.16-22 i686)


when trying to license my app. (Maya from AliasWavefront), flexlm cannot
query the dongle in the parrallel port.
'lmhostid -flexid ' simply returns "" as the flexid.

Both port and dongle works fine while running in windows.'
So either its a problem with redhat7 or Globetrotter's flexlm

Reproducible: Always
Steps to Reproduce:
1. insert dongle into parallel port
2. run lmhostid -flexid  
3.
	

Actual Results:  lmhostid returns an empty "" flexid string

Expected Results:  It should return the flexid of the dongle like: 7-b3423b
or similar

http://www.globetrotter.com/


the severity below doesnt have a matching line, this is quite severe since
you cant license software using dongles.
Comment 1 Need Real Name 2001-02-19 07:06:17 EST
It seems to be a flexlm problem, Im just now trying to confirm that flexlm on
Linux does not currently support flexid dongles
Comment 2 Michael K. Johnson 2001-02-21 10:58:26 EST
This looks very much like a flexlm problem, and we're going to assume
that it is such unless we find out information to the contrary.
Please re-open this bug report with that information if you get it.

Note You need to log in before you can comment on or make changes to this bug.