On Wed, Dec 19, 2012 at 4:22 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > > It works fine to just ssh in from somewhere else without needing > screen. The problem is when I forget and start the yum update from a > window where freenx on the same box is the parent session. I don't > need yet another way to connect - I'm looking for something to either > improve my memory (unlikely...) or to keep the freenx package update > from breaking the connection in progress when I forget and run it > there. > -- > Les Mikesell A wise man once told me: If you don't like things that use traditional unix tools for the purposes they were designed, why are you interested in using linux at all? -- Les Mikesell So if you don't want to use screen, which has its main purpose of preventing processes from getting killed when the terminal is killed, then how do you expect us to help? But seriously, the alias thing is a good idea. You can also have it check if its within screen instead of detecting freenx, which is probably a lot easier if you look at $TERM. Alternatively, you could exclude freenx from yum updates and have a cron job that emails you once a week if there's an update to it. At least that way you won't get bitten when it gets lumped into other updates. It seems strange that an update would kill an existing connection. Updates to other critical things like ssh have not done that in years. Maybe a bug to be filed with the package vendor? ❧ Brian Mathis