Project

General

Profile

Bug #11938

Deal with how NetworkManager dispatcher scripts are called on Stretch

Added by intrigeri about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
11/16/2016
Due date:
% Done:

100%

Feature Branch:
bugfix/11937-upgrade-network-manager
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/00-save-env: 6: [: =: unexpected o
Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/10-tor.sh: 7: [: =: unexpected ope
Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/60-tor-ready.sh: 4: [: =: unexpect

... which means that $1 is empty.

Associated revisions

Revision 5f51d1e8 (diff)
Added by intrigeri about 3 years ago

Deal with the fact that the NetworkManager dispatcher scripts are sometimes called with an empty first argument (Closes: #11938).

History

#1 Updated by intrigeri about 3 years ago

I've see these scripts called with an empty 1st arg, and the 2nd being "connectivity-change". Quoting $1 everywhere should deal with that.

#2 Updated by intrigeri about 3 years ago

  • Feature Branch set to bugfix/11937-upgrade-network-manager

#3 Updated by intrigeri about 3 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF