Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.system
Subject: Re: Can't Eject a Volume
Date: 21 Feb 2014 19:14:57 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 44
Message-ID: <bmpmthF3of8U1@mid.individual.net>
References: <1lh9o11.jdr30za7497aN%nicknaym@_remove_this_gmail.com.invalid> <le0f64$i8t$1@dont-email.me> <slrnlgc6tl.ku.g.kreme@oswin.local> <le5qqs$n2q$1@dont-email.me> <slrnlgdbbh.hco.g.kreme@oswin.local> <bmpf4dF1uueU2@mid.individual.net> <210220141307413164%nospam@nospam.invalid>
X-Trace: individual.net aQ9iRqcF5TqoFmWDbj5m3waizc072CnM7M9xZvZk/jRBbHBA8F
Cancel-Lock: sha1:htvz6dUDN9SkJ5TPNMe9w0N9HQI=
X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zk*i`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.system:56808

On 2014-02-21, nospam <nospam@nospam.invalid> wrote:
> In article <bmpf4dF1uueU2@mid.individual.net>, Jolly Roger
><jollyroger@pobox.com> wrote:
>
>> To expand on this, force quitting an application can cause any file that
>> the application currently has open to become corrupt, since it does not
>> give the application a chance to finish updating the file in question
>> and close it before quitting. Applications may have their own preference
>> files open, or other files on your startup volume. If an application's
>> preference file becomes malformed or corrupt, it can cause the
>> application in question to behave in unpredictable ways on subsequent
>> launches.
>
> that's possible, but very unlikely because files are written atomically.

mr.know-it-all won't be able to provide evidence that all (or even most)
files are written atomically by all applications. The fact is that
application developers may choose keep files open for relatively long
periods of time, and whether an application has a file open, or has
completed writing to that file, at any point in time cannot be predicted
ahead of time.

Now I predict mr.know-it-all will try to move the goal posts, which is
typical of his silly tit-for-tat arguments...

>> > Force quitting an app like the Finder where you are never sure of the
>> > state it is in is absolutely to be avoided.
>> 
>> I'm not sure I would consider Finder to be that fragile - certainly not
>> as fragile as other applications or system processes.
>
> nonsense. finder is one of the buggiest parts of os x and apple has
> shown no interest in fixing it.

Now he's trying to move the goal posts yet again. He ignores that we are
talking specifically about files open by the Finder. Now he's trying to
change the topic to general Finder bugs. Lame. That's not what we are
discussing here. Nice try, but no cigar, mr.know-it-all.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR