Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This is what lftp man page says about the cmd:fail-exit option:
cmd:fail-exit (boolean)
if true, exit when an unconditional (without || and && at
begin) command fails.
The description is misleading in two ways, or more precisely, mixing two different things together. First, lftp does not exit immediately after the failed command; instead, it waits for the user to input one more command (which is not executed). Second, it is this other command, not the failed one, which must not begin with a logical operator. The failed command can well be a conditional one:
# lftp -e 'set cmd:fail-exit yes'
lftp :~> !true
lftp :~> && !false
lftp :~> !true
#
To make the actual behaviour clear in the documentation, I propose the following formulation:
cmd:fail-exit (boolean)
if true, exit when a command fails and the following command is
unconditional (i.e. does not begin with || or &&). lftp exits
after the unconditional command is issued without executing it.
Version-Release number of selected component (if applicable):
lftp-4.0.9-5.el6.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0701.html
Description of problem: This is what lftp man page says about the cmd:fail-exit option: cmd:fail-exit (boolean) if true, exit when an unconditional (without || and && at begin) command fails. The description is misleading in two ways, or more precisely, mixing two different things together. First, lftp does not exit immediately after the failed command; instead, it waits for the user to input one more command (which is not executed). Second, it is this other command, not the failed one, which must not begin with a logical operator. The failed command can well be a conditional one: # lftp -e 'set cmd:fail-exit yes' lftp :~> !true lftp :~> && !false lftp :~> !true # To make the actual behaviour clear in the documentation, I propose the following formulation: cmd:fail-exit (boolean) if true, exit when a command fails and the following command is unconditional (i.e. does not begin with || or &&). lftp exits after the unconditional command is issued without executing it. Version-Release number of selected component (if applicable): lftp-4.0.9-5.el6.x86_64