This is a discussion on Console port causes ultra 60 to halt when unplugged within the comp.unix.solaris forums, part of the Solaris Operating System category; --> I am running Solaris 8, and I have a serial connection to my PC from my Ultra 60. Whenver ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am running Solaris 8, and I have a serial connection to my PC from my Ultra 60. Whenver I power down my PC my ultra 60 halts. I was wondering if anyone knows if there is a patch or a workaround so that this does not happen? Thanks! |
| |||
| On Fri, 29 Aug 2003, Packetshaper wrote: > I am running Solaris 8, and I have a serial connection to my PC from > my Ultra 60. Whenver I power down my PC my ultra 60 halts. I was > wondering if anyone knows if there is a patch or a workaround so that > this does not happen? man kbd -- Rich Teer, SCNA, SCSA President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-online.net |
| |||
| On Fri, 29 Aug 2003 17:32:34 GMT, Rich Teer <rich.teer@rite-group.com> wrote: >On Fri, 29 Aug 2003, Packetshaper wrote: > >> I am running Solaris 8, and I have a serial connection to my PC from >> my Ultra 60. Whenver I power down my PC my ultra 60 halts. I was >> wondering if anyone knows if there is a patch or a workaround so that >> this does not happen? > >man kbd Thanks! That is exactly what I need. I am not near my computer to test it right now, did I do this right. I did kbd -a disable Is that going to work for the serial port as well? |
| |||
| In article <hp3vkv47tbvs0sst8uckafk3fq5s59k70u@4ax.com>, Packetshaper <packetshaper@hotmail.com> wrote: >On Fri, 29 Aug 2003 17:32:34 GMT, Rich Teer <rich.teer@rite-group.com> >wrote: > >>On Fri, 29 Aug 2003, Packetshaper wrote: >> >>> I am running Solaris 8, and I have a serial connection to my PC from >>> my Ultra 60. Whenver I power down my PC my ultra 60 halts. I was >>> wondering if anyone knows if there is a patch or a workaround so that >>> this does not happen? >> >>man kbd > > >Thanks! That is exactly what I need. I am not near my computer to >test it right now, did I do this right. I did kbd -a disable > >Is that going to work for the serial port as well? I would suggest a 'kbd -a alternate' that leaves you with the ability to get to the console should you want to. Yes it works for the serial port aswell. /wfr Fredrik -- Fredrik Lundholm dol @ ce.chalmers.se |
| |||
| Packetshaper <packetshaper@hotmail.com> wrote: > Rich Teer <rich.teer@rite-group.com> wrote: > >On Fri, 29 Aug 2003, Packetshaper wrote: > > > >> I am running Solaris 8, and I have a serial connection to my PC from > >> my Ultra 60. Whenver I power down my PC my ultra 60 halts. I was > >> wondering if anyone knows if there is a patch or a workaround so that > >> this does not happen? > > > >man kbd > > Thanks! That is exactly what I need. I am not near my computer to > test it right now, did I do this right. I did kbd -a disable > > Is that going to work for the serial port as well? Youz expected to finish the exercise yerself. -am © 2003 |
| |||
| Rich Teer wrote: > On Fri, 29 Aug 2003, Packetshaper wrote: > > >>Thanks! That is exactly what I need. I am not near my computer to >>test it right now, did I do this right. I did kbd -a disable >> >>Is that going to work for the serial port as well? > > > Yes, but kbd -a alternate might be a better choice. On top, you might want to add * set abort_enable=false * to your /etc/system file Martin |
| |||
| Martin Schoen <noreply@vamosphoto.de> writes: >Rich Teer wrote: >> >> Yes, but kbd -a alternate might be a better choice. > >On top, you might want to add > >* >set abort_enable=0 >* > >to your /etc/system file > No. Do *NOT* mess with the /etc/system file if your kbd man page documents the "-a disable" option or the "-a alternate". There is no advantage or enhancement that the /etc/system file can offer. You will only confuse yourself. -Greg -- Do NOT reply via e-mail. Reply in the newsgroup. |
| |||
| Greg Andrews wrote: > > No. Do *NOT* mess with the /etc/system file if your kbd man page > documents the "-a disable" option or the "-a alternate". There is > no advantage or enhancement that the /etc/system file can offer. > You will only confuse yourself. Do you *have to* 'sys-unconfig' your system to change an ip address? Do you *have to* use admintool to handle users? As always TMTOWTDI, choose your preferred method. I wouldn't call editing system files as 'messing' with them. Just my 0.02$ Martin |
| ||||
| Martin Schoen <noreply@vamosphoto.de> writes: >Greg Andrews wrote: >> >> No. Do *NOT* mess with the /etc/system file if your kbd man page >> documents the "-a disable" option or the "-a alternate". There is >> no advantage or enhancement that the /etc/system file can offer. >> You will only confuse yourself. > >Do you *have to* 'sys-unconfig' your system to change an ip address? > Do you remember to remove /var/spool/tmp/temp when you change your print servers hostname/ip? Most people don't when they change it by hand, but sys-unconfig remembers to do it. > >Do you *have to* use admintool to handle users? > Ugh, no. Admintool has been obsolete since Solaris 7 or 8. > >As always TMTOWTDI, choose your preferred method. >I wouldn't call editing system files as 'messing' with them. > Except the thing you suggest is an unnecessary action that adds no benefit compared to using the kbd command and /etc/default/kbd file. Editing /etc/system that can prevent your machine from booting, so it's a potentially dangerous action. A mistake in editing the file can require you to boot from cdrom, then fsck and mount the root filesystem before you can fix the error. If your root filesystem is mirrored, it takes even more steps to remove the mistake. Meanwhile, your machine is down. So editing /etc/system is not, as you say, merely an alternative method to preventing the keyboard/serial abort. It's a method that is potentially dangerous to the health of your machine. It's more dangerous, but it offers no benefits compared to the safer method. A good sysadmin will see this and decide to not use the more dangerous method. Putting yourself at risk, even only a small risk, is not what a good sysadmin does when the risk is not necessary. That is what I pointed out in this thread. -Greg -- Do NOT reply via e-mail. Reply in the newsgroup. |