Actually, all you really should have needed to do was run the script in the background (ie ~admin/path/to/my/script &). Yet, you'll probably find that if you were to try to run any binaries (or scripts) which read from/write to a terminal (like one of the /dev/tty* devices) or pseudo-terminal (like one of the /dev/pts/* devices) via that script, then those binaries will probably behave a little differently than you might expect. In that case, you have a couple options: force the binaries in question to run interactively, handle the respective SIGTTIN and/or SIGTTOU signals for those binaries.