csh is not compatible #316

New Issue

ungleich-gitea · 2021-11-20T15:24:13Z

ungleich-gitea commented

2021-11-20 15:24:13 +00:00

Created by: pestaa

csh is the default shell on FreeBSD 9.0. Although it is supposed to be POSIX-compatible, it does not support

key=value /bin/sh -e command...

syntax and it stops with error

value=key: Command not found.

This issue is easily fixable by changing the default shell even to plain sh, but it is one caveat that might be noted to FreeBSD developers.

*Created by: pestaa* `csh` is the default shell on FreeBSD 9.0. Although it is supposed to be POSIX-compatible, it does not support ``` key=value /bin/sh -e command... ``` syntax and it stops with error ``` value=key: Command not found. ``` This issue is easily fixable by changing the default shell even to plain `sh`, but it is one caveat that might be noted to FreeBSD developers.

ungleich-gitea closed this issue

2021-11-20 15:24:13 +00:00

ungleich-gitea commented

2021-11-20 15:53:05 +00:00

Created by: telmich

Added a permanent entry in the log directory: doc/dev/logs/2012-05-31.csh-compatibilty

*Created by: telmich* Added a permanent entry in the log directory: doc/dev/logs/2012-05-31.csh-compatibilty

ungleich-gitea commented

2021-11-20 15:53:07 +00:00

Created by: telmich

cat * | /bin/sh -s could also work, needs testing though

*Created by: telmich* cat \* | /bin/sh -s could also work, needs testing though

ungleich-gitea commented

2021-11-20 15:53:08 +00:00

Created by: telmich

Ha!

I've found a solution!

We can setup the variables locally (within a specific context/call) and then send it via the ssh option
"-o SendEnv name"

Do you want to give it a try to implement this in a feature branch?

*Created by: telmich* Ha! I've found a solution! We can setup the variables locally (within a specific context/call) and then send it via the ssh option "-o SendEnv name" Do you want to give it a try to implement this in a feature branch?

ungleich-gitea commented

2021-11-20 15:53:09 +00:00

Created by: telmich

Hey Istvan,

Istvan Beregszaszi [Sat, Apr 14, 2012 at 07:59:36AM -0700]:

csh is the default shell on FreeBSD 9.0. Although it is supposed to be POSIX-compatible, it does not support
key=value /bin/sh -e command...
syntax and it stops with error
value=key: Command not found.

Maybe there is even a way to work around this issue:

Maybe we can join / setup the variables inside the /bin/sh call and thus
ignoring whatever shell root is configured for.

Haven't checked the docs (falling almost asleep, but wanted to
write down this comment), but something like this could work:

/bin/sh -e key=value key2=value2 command...

And if not this, the ugly version, creating a file on the remote side
containing

key=value
key2=value2


and the executing the file with /bin/sh would work.
I consider the second approach ugly, but a possible way. I imagine we

could figure some not-so-bad syntax to avoid this.
Cheers,
Nico
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

*Created by: telmich* Hey Istvan, Istvan Beregszaszi [Sat, Apr 14, 2012 at 07:59:36AM -0700]: > `csh` is the default shell on FreeBSD 9.0. Although it is supposed to be POSIX-compatible, it does not support > > ``` > key=value /bin/sh -e command... > ``` > > syntax and it stops with error > > ``` > value=key: Command not found. > ``` Maybe there _is_ even a way to work around this issue: Maybe we can join / setup the variables inside the /bin/sh call and thus ignoring whatever shell root is configured for. Haven't checked the docs (falling almost asleep, but wanted to write down this comment), but something like this could work: ``` /bin/sh -e key=value key2=value2 command... ``` And if not this, the ugly version, creating a file on the remote side containing key=value key2=value2 <code> and the executing the file with /bin/sh would work. I consider the second approach ugly, but a possible way. I imagine we could figure some not-so-bad syntax to avoid this. Cheers, ## Nico PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0

ungleich-gitea commented

2021-11-20 15:53:11 +00:00

Created by: jdguffey

Indeed. This is an issue that I have run into myself. To solve it, I made /bin/sh the default shell for root on all new FreeBSD deployments. I didn't really think anything of it, but now that you mention it, I would have to agree that perhaps this caveat should be listed in doc/man/man1/cdist.text or doc/man/man7/cdist-quickstart.text.

Thoughts on this, Nico?

*Created by: jdguffey* Indeed. This is an issue that I have run into myself. To solve it, I made /bin/sh the default shell for root on all new FreeBSD deployments. I didn't really think anything of it, but now that you mention it, I would have to agree that perhaps this caveat should be listed in doc/man/man1/cdist.text or doc/man/man7/cdist-quickstart.text. Thoughts on this, Nico?

Sign in to join this conversation.