bin/pluto_updown - Issue 6508016: vpn-manager: Add l2tp/ipsec vpn manager

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: bin/pluto_updown

Issue 6508016: vpn-manager: Add l2tp/ipsec vpn manager (Closed) Base URL: ssh://git@gitrw.chromium.org:9222/vpn-manager.git@master

Patch Set: tweak Created 9 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 # Copyright (c) 2011 The Chromium OS Authors. All rights reserved.

	2 # Use of this source code is governed by a BSD-style license that can be

	3 # found in the LICENSE file.

	4

	5 # The syslog tag for all logging we emit.

	6 TAG="$(basename $0)[$$]"

	7

	8 log() {

	9 logger -t "${TAG}" "$@"

	10 }

	11

	12 log "Received PLUTO_VERB=$PLUTO_VERB for pid $IPSEC_MANAGER_PID"
	petkov 2011/03/04 18:42:56 use {} around variables? is there a good reason to use {} around variables? is there a good reason to pass arguments through environment variables? kmixter1 2011/03/05 02:48:59 Originally I was going to use SIGUSR1 to notify IP Show quoted text On 2011/03/04 18:42:56, petkov wrote: > use {} around variables? is there a good reason to pass arguments through > environment variables? Originally I was going to use SIGUSR1 to notify IPSEC_MANAGER_PID when this layer is up, but the daemon runs as a different user, so that wouldn't work. Removing the setting of PID since it's no longer used.
	13

	14 if [ "$PLUTO_VERB" = "up-host" ]; then

	15 touch /tmp/ipsec-up
	petkov 2011/03/04 18:42:56 is this 3-space indent? is this 3-space indent? kmixter1 2011/03/05 02:48:59 Done. Show quoted text On 2011/03/04 18:42:56, petkov wrote: > is this 3-space indent? Done.
	16 fi

OLD	NEW