My situation is similar to the one outlined here, but I don't want the user to be able to log out either.

Basically I want this terminal to always be running this application. I have it running on startup (using tty1.conf to auto-login, .profile to launch the app). But if the user kills the application (ctrl-c), I want it to start up again.

I know it's possible to do on FreeBSD using gettytab, but I'm not sure how it would be done on linux (Ubuntu 11.10 Server). A nice thing about the BSD method was that you could escape the trap using Alt+F7, bringing you to a shell.

Greetings,

Well, I know that the equivalent to FreeBSD's getty is agetty in linux, though, as the man page states:Now, I have a couple questions about this:

1. This application will be running on that terminal, no matter what happens with the rest of the system?
2. Will there be an actual user login, or are you going to force a specific non-privileged account to login without a password?
3. What is expected to happen to the terminal and/or app that's running in it when the system receives the 'shutdown' or 'reboot' (or any equivalent) commands?

HTH. Let us know.

If you look at /etc/inittab, you can see how login or gdm are started & respawned. But why isn't it started as a service?

Also, inittab may go away after systemd is used exclusively.

Yes, it is supposed to be a single-purpose terminal for running only that application.

I'm currently doing a forced login on an unprivileged account using /etc/tty1.conf

Those are fine; I don't expect the script to prevent shutdown or anything. Just needs to start back up when the system restarts.

Try stty -isig in your script to disable SIGINT, SIGQUIT, and SIGSTOP from key bindings.
Kevin Barry

you can start it also in the background

Assuming the terminal is actually needed for interaction, the process will sleep if it tries to read from the terminal until it's in the foreground.
Kevin Barry