summaryrefslogtreecommitdiffstats
path: root/usr.bin
diff options
context:
space:
mode:
authormjacob <mjacob@FreeBSD.org>2002-02-21 01:56:08 +0000
committermjacob <mjacob@FreeBSD.org>2002-02-21 01:56:08 +0000
commitd4fb4b6c57e2fe3fc6ff6d3bfc8f3b97d3501b89 (patch)
treeb38a3e6d077bd845fbb6aeee0a6babb40d1387d5 /usr.bin
parentcf06489c2d4eab716cf9a022f801ae33d4a2a1ba (diff)
downloadFreeBSD-src-d4fb4b6c57e2fe3fc6ff6d3bfc8f3b97d3501b89.zip
FreeBSD-src-d4fb4b6c57e2fe3fc6ff6d3bfc8f3b97d3501b89.tar.gz
Fix a problem where a local loop disk logs out- and we get a PORT LOGGED
OUT status. We are, apparently, required to force the f/w to log back in if we want to try and talk to that disk again. This means either issuing a LOGIN LOCAL LOOP PORT mailbox command, or by issuing a LIP. I've elected to issue a LIP because this has a better chance of waking up the disk which clearly just crashed and burned. These should not occur at all. If they do, they should be darned rare. MFC after: 1 week
Diffstat (limited to 'usr.bin')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud