Update transport.asciidoc

[lhirlimann]

Add an example on what to change to the unix configuration for having long keep_alive sessions.

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you built your formula locally prior to submission with gradle check?
• If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?
• If you are submitting this code for a class then read our policy for that.

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

@lhirlimann please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[lhirlimann]

@lhirlimann please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

Can't find how to do it since I don't have a fork, I used the UI from the docs page to make the edit.

[leemthompo]

@DaveCTurner any SME input on this one? :)

[DaveCTurner]

Could we write this similarly to how it's done on https://www.elastic.co/guide/en/elasticsearch/reference/current/system-config-tcpretries.html?

Also I don't think we should be suggesting changing tcp_keepalive_probes.

[leemthompo]

Important

Elastic documentation is migrating to Markdown for version 9.0+. See the migration guide for details.

ℹ️ What's happening?

• Starting January 29, we will start closing all unmerged documentation PRs targeting main/master
• We're migrating from AsciiDoc to Markdown for 9.0+
• 9.0 docs will be frozen from January 29 until February 20 2024
• NOTE: PRs that include both code and documentation changes will remain open

What do I need to do?

For <=8.x docs:

1. Rebase your PR to target the relevant 8.x branch instead
2. The content can remain in AsciiDoc format

For 9.0+ docs:

Option 1:

• Draft docs in Markdown
• Once migration freeze ends, find the relevant page in the new docs system and use the edit options to submit your changes

Option 2:

• Open an issue in elastic/docs-content

💡 Need help?

1. For Elasticians: Ask in #docs Slack channel
2. For external contributors: Open an issue in elastic/docs-content