Re:Show HN: A pure bash web server. No netcat, socat, etc.
by goombacloud on Tuesday January 04, 2022 @11:40AM
(#29796740)
To spare you the trap you can open the file as FD in your bash process (e.g., exec {my_fd}>"$TMPFILE") and then directly delete it before doing anything else, and use the /proc handle to access it ("/proc/$$/fd/${my_fd}")
[ Parent
| on HN ]
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by goombacloud on Friday January 07, 2022 @11:57AM
(#29841530)
One more fun experiment: avoid the tempfile on disk/tmpfs by storing data into the pipe connecting two processes, where the first one can already exit for the pipe to give EOF when reading beyond the buffered data.
true | sleep infinity &
STDINPID="$!"
TMPPIPE="/proc/$STDINPID/fd/0"
echo hello > "$TMPPIPE"
echo write more > "$TMPPIPE"
cat "$TMPPIPE"
echo write again > "$TMPPIPE"
cat "$TMPPIPE"
kill -9 "$STDINPID" # clean up pipe
Now I would like to avoid the additional process by using the current shell process instead.
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by goombacloud on Friday January 07, 2022 @12:14PM
(#29841714)
Still needs to spawn a temporary process but it can be killed early:
true | sleep infinity &
STDINPID="$!"
exec {mypipe}<"/proc/$STDINPID/fd/0" # hijack FD
TMPPIPE="/proc/$$/fd/${mypipe}"
disown "$STDINPID" # suppress killed message on stderr
kill -9 "$STDINPID" # clean up process now already
echo hello > "$TMPPIPE"
echo write more > "$TMPPIPE"
cat "$TMPPIPE"
echo write again > "$TMPPIPE"
cat "$TMPPIPE"
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by dzove855 on Friday January 07, 2022 @02:48PM
(#29843793)
Since now, multiple concurrent connections will work after my patch. (Need to add subshell) i will need to consider using fd as output cache. Instead of temporary files.
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by Klasiaster on Friday January 07, 2022 @04:06PM
(#29844820)
This here is a simple echo server that uses tr to uppercase:
exec {checkfd}>/dev/null
CHECKFDPATH="/proc/$$/fd/${checkfd}"
(while [ -e "$CHECKFDPATH" ]; do sleep 1; done) > >(true) &
STDINPID="$!"
WRITER="/proc/$STDINPID/fd/1"
while IFS= read -r LINE; do
# only echo lines if we didn't close the connection yet
if [ -e "$CHECKFDPATH" ]; then
echo "$LINE" | tr '[:lower:]' '[:upper:]' > "$WRITER"
if [ "$LINE" = "bye" ]; then
exec {checkfd}<&-
fi
else
echo "received while closed: $LINE"
fi
done < <(nc -q 1 -l 8080 < "$WRITER")
if [ -e "$CHECKFDPATH" ]; then
# close checkfd to close writer pipe
exec {checkfd}<&-
fi
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by Klasiaster on Friday January 07, 2022 @04:45PM
(#29845256)
This variant here works a bit different:
exec {checkfd}>/dev/null
CHECKFDPATH="/proc/$$/fd/${checkfd}"
(while [ -e "$CHECKFDPATH" ]; do sleep 1; done) > >(true) &
STDINPID="$!"
disown "$STDINPID"
READER="/proc/$STDINPID/fd/1"
{ while IFS= read -r LINE; do
echo "$LINE" | tr '[:lower:]' '[:upper:]'
if [ "$LINE" = "bye" ]; then
echo exiting > /dev/stderr
break
fi
done < "$READER" ; kill -9 "$STDINPID" 2>/dev/null || true ; } | { nc -q 1 -l 8080 > "$READER" ; kill -9 "$STDINPID" 2>/dev/null || true ; }
exec {checkfd}<&-
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by dzove855 on Friday January 07, 2022 @04:19PM
(#29844979)
No need of tr here in your example.
The fd will only be used to stor it temporary since, we first need to sent headers, and the headers need to be sent before the bofy. The server base os working fine now with accept and a patch request os already sent to bash. So probaböy on the next release accept will be full usable.
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by Klasiaster on Friday January 07, 2022 @02:40PM
(#29843702)
Seems "sleep 60" is safer and still good enough unless the system is completely overloaded.
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by stouset on Tuesday January 04, 2022 @03:49PM
(#29800257)
That's an awesome technique, thanks for it! It is Linux-specific though.
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by Klasiaster on Tuesday January 04, 2022 @05:21PM
(#29801475)
It's also useful for signaling between processes to have them continue doing something as long as this proc path exists (the fd can also just be backed with >/dev/null instead of a real file that needs to be removed)
Re:Show HN: A pure bash web server. No netcat, socat, etc.
by labawi on Thursday January 06, 2022 @03:55PM
(#29830019)
Normally, the pid and fd could be reused, so you should either make it a known unique path and verify it's still the same, lock the pid via some means (not sure if and how it's possible), or use another technique.