Thanks for doing the research into this for us Tom. Not good news, but at least now we know and can start thinking about how to redesign the application.
Regards, Trev Tom Whitten wrote: > Trevor Watson writes: >> Hi, >> >> I hope this is the correct alias to use for this question. If not, please >> feel >> free to direct me elsewhere. >> >> We have an application which applies patches to a system in single-user mode. >> >> For various (mostly historical) reasons, it runs as a legacy app in >> single-user mode, and we have found that the user cannot use Ctrl-C on it on >> Solaris 10, although this works perfectly well on S8 & 9. >> >> I appreciate that the application is not very well behaved, but is there any >> way we can configure the legacy SMF starter to allow the app to receive >> Ctrl-C >> from the console? >> >> Thanks, >> Trev > > Trev, > > The reason that you cannot use Ctrl-C in Solaris 10 is that SMF runs legacy > services without a control terminal. Any output that was sent to the > console in pre-SMF days is now captured in the appropriate milestone log > file in /var/svc/log. > > The reason that SMF does this is so that it can do as many things in > parallel as possible. Storing service output in the appropriate log file > makes it easier to diagnose failures and avoids a jumble of messages on the > console. Starting services in parallel allows for faster boots. > > I've been unable to find any way to override this behavior for your > application. Since you are running in single-user mode, however, you can > login and use kill -3 on the process. > > tom -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20070314/2b5f97a6/attachment.bin>
