Lloyd Kvam writes:
> Should I simply disable IPMI or is it likely to be useful even in my
> circumstances?
Do you have any need to manage your server remotely using the
functionality that IPMI provides? How easy is it for you to
physically access your server?
I've been giving IPMI some thoug
When:February 20, 2013 7PM (6:30PM for Q&A)
Topic: IPV6 on a home network
Moderators:Daniel Hagerty
Location: MIT Building E51, Room 315
Summary
Deploying IPv6 on a home network
Abstract
Dan Hagerty talks about IPv6 connectivity on your own local home
network. Dan's slides are on the BLU website
Hey, all. For various esoteric reasons, I'm wondering if someone can
tell me the answer to this question.
If process A is reading from a file, and process B deletes it, process
A can continue to read from it until... well, until it stops reading
from it. Can that space that the file takes up
On Tue, 2013-02-19 at 11:16 -0500, Kevin D. Clark wrote:
> Lloyd Kvam writes:
>
> > Should I simply disable IPMI or is it likely to be useful even in my
> > circumstances?
>
> Do you have any need to manage your server remotely using the
> functionality that IPMI provides? How easy is it for y
>Can that space that the file takes up be overwritten during
>this interim? Or does the OS hold the inode sacrosanct until
>both references AND processes are no longer making use of it?
Right - the OS's official record of a file's state is the
(in-memory copy of the) inode - the directory entri
IPMI was involved with reestablishing communications with
your Dom-0 ? Interesting. Was that via Serial-Over-LAN?
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
On Tue, Feb 19, 2013 at 2:40 PM, Ken D'Ambrosio wrote:
> If process A is reading from a file, and process B deletes it, process
> A can continue to read from it until... well, until it stops reading
> from it.
It can also seek it, write to it, etc. This condition persists
until the process cal
Ben Scott writes:
>
> On Tue, Feb 19, 2013 at 2:40 PM, Ken D'Ambrosio wrote:
> > If process A is reading from a file, and process B deletes it, process
> > A can continue to read from it until... well, until it stops reading
> > from it.
[...]
> > Can that space that the file takes up be overwrit
> Some processes do this deliberately for temporary files:
> They create/open a new file and then immediately unlink it.
> This yields an "anonymous file", which won't need to be specially
> cleaned up, even if the program crashes.
Bad Guys do this, too, because such "deleted" files aren't
easil
