# Page Not Found

The URL `system_call_huo_bust/sendto_yu_recvfrom__lai_dian_dgram` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [5.8. sendto() 與 recvfrom()－ 來點 DGRAM](https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5sendto.md)
- [5.10. getpeername()－你是誰？](https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5getpeername.md)
- [5.1. getaddrinfo()－準備開始！](https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5-1-getaddrinfo-start.md)
- [5.11. gethostname()－我是誰？](https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5gethostname.md)
- [5.4. connect()，嘿！你好。](https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5connect.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://beej-zhtw-gitbook.netdpi.net/05-system-call-or-bust/5sendto.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://beej-zhtw-gitbook.netdpi.net/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://beej-zhtw-gitbook.netdpi.net/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/05-system-call-or-bust/5sendto.md`).

You may also use `Accept: text/markdown` header for content negotiation.