@@ -58,9 +58,10 @@ terminating processes started by it or terminating the startup script itself (on
58
58
Linux,` ps ` and` kill ` are useful tools).
59
59
60
60
For tips on how to write a startup script that doesn't run forever, see the
61
- [ ` startup_script ` ] ( #startup_script ) section. For more ways to override the
62
- startup script behavior, see the
63
- [ ` startup_script_behavior ` ] ( #startup_script_behavior ) section.
61
+ [ ` startup_script ` ] ( https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script )
62
+ section. For more ways to override the startup script behavior, see the
63
+ [ ` startup_script_behavior ` ] ( https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script_behavior )
64
+ section.
64
65
65
66
Template authors can also set the
66
67
[ startup script behavior] ( https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script_behavior )
@@ -75,9 +76,9 @@ be aware that programs, files, or settings may be missing from your workspace.
75
76
This can happen if the
76
77
[ startup script] ( https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script )
77
78
is still running or has exited with a non-zero status (see
78
- [ startup script error] ( #startup-script-error ) ). No action is necessary, but you
79
- may want to
80
- [ start a new shell session] ( #session-was-started-before-the-startup-script-finished-web-terminal )
79
+ [ startup script error] ( #startup-script-exited-with-an- error ) ). No action is
80
+ necessary, but you may want to
81
+ [ start a new shell session] ( #session-was-started-before-the-startup-script-finished )
81
82
after it has completed or check the
82
83
[ startup script logs] ( #debugging-the-startup-script ) to see if there are any
83
84
issues.