Bug 53430 - pilot-xfer ignores environment variables
Summary: pilot-xfer ignores environment variables
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pilot-link
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-09-08 18:36 UTC by William M. Quarles
Modified: 2008-05-01 15:38 UTC (History)
0 users

Clone Of:
Last Closed: 2001-09-08 18:36:25 UTC

Attachments (Terms of Use)

Description William M. Quarles 2001-09-08 18:36:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010628

Description of problem:
If the environment variables PILOTRATE and PILOTPORT are set using bash,
the pilot-xfer program ignores these and simply synchronizes using the
default device or the device specified on the command line, and it uses the
default rate of 9600 baud

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Run in X so that multiple terminals can be opened.
2.Type PILOTRATE=115200 at the bash prompt in a terminal window.
3.Type PILOTPORT=/dev/ttySx where x is the number of the serial port to be
4.Verify that these variables have been set correctly using, for example,
5.Run "pilot-xfer -b pilot-link", for example.  It will say "Port: /dev/pilot"
6.Run stty -F /dev/ttySx, and you will see that the baud rate has been set
to 9600, even if you set it to a different value earlier.

Actual Results:  Synchonization is pretty darn slow, and not necessarily on
the port that you want it to be.

Expected Results:  The synchonization should take place at the port and
baud rate specified by the environment variables.

Additional info:  Also tried installing the latest RawHide package, didn't
help the issue.

Comment 1 Ngo Than 2001-09-19 20:19:19 UTC
It's fixed in pilot-link-0.9.5-9. You will find it in next rawhide release.

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