Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • SSH fun (Score:3, Informative)

    I had that one bite me once, too - luckily I still had one of my ssh sessions connected. The key is to not do the installkernel and installworld steps when you're going to be disconnecting from the system. You can toss the buildworld and buildkernel into a screen and forget about them, but when you come back to do the install steps and mergemaster, make certain that you complete the process and reboot!

    Most times ssh doesn't change significantly, but when it does, you get in trouble with things like this

    • In ideal world nobody should do system upgrades remotly: i.e. you should be able to access system console and should do everything in single user. *sigh*

      I found SSH to be broken after I had ran mergemaster. I suspect that I messed with PAM settings. I did touched SSH configs too but it should not affect SSH daemon as I haven't restarted it.

      Luckily I did run installworld before logging off and I have very slim hope that newly installed SSH will be compatible with new configs. I'll find it tomorrow when I

      --

      Ilya Martynov (http://martynov.org/ [martynov.org])

      • I do remote system upgrades on a regular (read almost daily) basis - if you practice enough with non-critical systems and get a good, functional procedure down, it can go off flawlessly. On some systems (pretty much everything I have in production, for example) you simply can't afford the amount of downtime that going down into single user even for just a couple of quick reboots and installs will generate.

        If you ran installworld and mergemaster before logging off, you should be good to go when you reboot

        • I've been reading freebsd maillists for quite long time and I've seen remote upgrades discussed many times. In short conclusion I've drawn from these discussions is that strictly speaking non-single user upgrades are not supported and in general bad thing. There are many reasons why. Risk of broken networking, risk of unbootable system, undefined state of systen which may lead to security compromise. If you use security levels you will have to disable them and reboot without them into multy-user before doing upgrade. This again increases risks of security compromises. Having said this I must admit that I do remote upgrades from time to time and in reality I have no choice.
          --

          Ilya Martynov (http://martynov.org/ [martynov.org])