Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Here $SSHTIMEOUT not display proper value #1729

Open
mahadevanrm opened this issue Jul 31, 2017 · 2 comments
Open

Here $SSHTIMEOUT not display proper value #1729

mahadevanrm opened this issue Jul 31, 2017 · 2 comments

Comments

@mahadevanrm
Copy link

[Unit]
Description=SSH Per-Connection Server
After=syslog.target

[Service]
EnvironmentFile=-/etc/default/dropbear
#ExecStartPre=/ect/scripts/ssh_timeout.sh
ExecStartPre=/bin/sh -c 'SSHTIMEOUT=$(/bin/cat /etc/atom/defaults/syscfg_baseline.db | /bin/grep ssh_timeout | /bin/cut -d "=" -f2)'
ExecStart=/usr/sbin/dropbear -i -I $SSHTIMEOUT -r /var/tmp/dropbear_rsa_host_key -p 22 $DROPBEAR_EXTRA_ARGS
ExecReload=/bin/kill -HUP $MAINPID
StandardInput=socket

@mahadevanrm
Copy link
Author

Can any one help on this?

@berglh
Copy link

berglh commented Aug 11, 2017

@mahadevanrm This looks more like a systemd problem than a fleet problem. You are setting a variable inside ExecStartPre inside sh. That variable is not then available to ExecStart. You'd be better of doing something like:

ExecStart=/bin/sh -c 'SSHTIMEOUT=$(/bin/cat /etc/atom/defaults/syscfg_baseline.db | /bin/grep ssh_timeout | /bin/cut -d "=" -f2); /usr/sbin/dropbear -i -I $SSHTIMEOUT -r /var/tmp/dropbear_rsa_host_key -p 22 ${DROPBEAR_EXTRA_ARGS}'

Also fleet has been deprecated, if you're like me still using it, welcome to the ghost town 👻🌆

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants