SAM disables Ctrl-c (^C)

[Bolek Mynarski]

I ran into a pecular situation. I developed a bunch of scripts for our sysadmins (create account, lookup and so on) and when I run them from shell (meaning after loging in you obtain a shell access), they behave the way I expect them to. After logging in and running sam interactively, they still work.

However, when I limit my admins to run SAM immediatly after they log on (they never see shell prompt), Ctrl-c is disabled.

Is this an expected behaviour or if not, how can I prevent it from happening?

Thanks.

[Stefan Farrelly]

I believe its expected behaviour, SAM disables CTRL-C when your running it, this is to stop an inadvertant Ctrl-C at a critical time (like doing something with disks) which could seriously screwup your system.

[John Meissner]

I believe this is expected also. I the ^C is set in the .profile or /etc/profile. when using SAM as the start program their profile does not run. hence the ^C will not work. this is, I believe, to keep the user from gaining shell access.