Searched refs:script (Results 1 – 25 of 66) sorted by relevance
123
/busybox-1.35.0/util-linux/ |
D | scriptreplay.c | 30 const char *script = "typescript"; in scriptreplay_main() local 40 script = argv[2]; in scriptreplay_main() 46 fd = xopen(script, O_RDONLY); in scriptreplay_main()
|
/busybox-1.35.0/shell/ash_test/ash-redir/ |
D | redir_script.tests | 17 # One of the fds is open to the script body 24 && { echo "Ok: script fd is not closed"; exit 0; } 26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11: 29 && { echo "Ok: script fd is not closed"; exit 0; } 33 && { echo "Ok: script fd is not closed"; exit 0; } 35 echo "Bug: script fd is closed"
|
D | redir_script.right | 1 Ok: script fd is not closed
|
D | redir_to_bad_fd.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir_to_bad_fd255.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir_to_bad_fd3.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir4.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir5.tests | 6 # 2. Failure will result in this script hanging
|
/busybox-1.35.0/shell/hush_test/hush-redir/ |
D | redir_script.tests | 17 # One of the fds is open to the script body 24 && { echo "Ok: script fd is not closed"; exit 0; } 26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11: 29 && { echo "Ok: script fd is not closed"; exit 0; } 33 && { echo "Ok: script fd is not closed"; exit 0; } 35 echo "Bug: script fd is closed"
|
D | redir_script.right | 1 Ok: script fd is not closed
|
D | redir_to_bad_fd.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir_to_bad_fd255.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir_to_bad_fd3.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir4.tests | 1 # ash uses fd 10 (usually) for reading the script
|
D | redir5.tests | 6 # 2. Failure will result in this script hanging
|
/busybox-1.35.0/examples/shutdown-1.0/ |
D | README | 9 # /app/shutdown-1.0/script/shutdown: 11 ln -s /app/shutdown-1.0/script/shutdown /sbin/halt 12 ln -s /app/shutdown-1.0/script/shutdown /sbin/reboot 13 ln -s /app/shutdown-1.0/script/shutdown /sbin/poweroff 30 cd script && ./hardshutdown.make.sh
|
/busybox-1.35.0/docs/ |
D | embedded-scripts.txt | 11 script: it will probably need some external commands. If these are 15 custom script and the full-featured scripted applet. 20 When embedded script support is enabled the BusyBox build process 28 Adding a custom script is as simple as running the following sequence 46 Suppose we want to make a shell script version of the sample applet 47 from the New Applet HOWTO. First we'd have to write a script (vaguely) 74 dependencies the script has. No external commands are used by our mu 75 script, but it does depend on optional shell features. We can ensure 85 //config: mu is implemented as a shell script. It requires support
|
/busybox-1.35.0/miscutils/ |
D | dc.c | 272 bool script = 0; in dc_main() local 283 script = 1; in dc_main() 287 script = 1; in dc_main() 300 } else if (!script) { in dc_main()
|
/busybox-1.35.0/examples/var_service/dhcp_if/ |
D | run | 23 --script="$pwd/dhcp_handler"
|
/busybox-1.35.0/shell/hush_test/hush-parsing/ |
D | groups_and_keywords2.tests | 7 # This is an error, and it aborts in script
|
/busybox-1.35.0/shell/ash_test/ash-parsing/ |
D | groups_and_keywords2.tests | 7 # This is an error, and it aborts in script
|
/busybox-1.35.0/examples/var_service/ |
D | README | 36 In runit parlance a "service" is simply a directory containing a script 50 You can debug an individual service by running its SERVICE_DIR/run script. 67 Runs a getty on <tty>. (run script looks at $PWD and extracts suffix 103 udhcpc on other interfaces (var_service/dhcp_if/run script uses _foo suffix 111 This is an example of service with has a "finish" script. If downed ("sv d"), 143 "Firewall" script, although it is tasked with much more than setting up firewall. 165 at the very beginning of fw/run script, not at the end. 167 Therefore, any "sv u fw" command by any other script "undoes" o(ne-shot) 171 This mechanism is the reason why fw is a service, not just a script. 173 System administrators are expected to edit fw/run script, since [all …]
|
/busybox-1.35.0/scripts/kconfig/lxdialog/ |
D | BIG.FAT.WARNING | 3 kernel configuration script, and subsequently adapted for busybox.
|
/busybox-1.35.0/networking/udhcp/ |
D | dhcpc.h | 19 const char *script; /* User script to run at dhcp events */ member
|
/busybox-1.35.0/shell/ash_test/ash-signals/ |
D | signal9.tests | 1 # Note: the inner script is a test which checks for a different bug
|
123