OD 10.8 All dates modified for home folders & files changes on login

We upgraded our network server to 10.8 recently, and now whenever a user logs on, all the files & folders in their home reset the date modified to the login time. It's the most bizarre glitch I've ever seen.
Possibly, but not likely related, their mouse settings (or at least natural scrolling setting) are not retained.
Has anyone else encountered this weird behavior? New accounts/imported accounts are all effected. Doesnt matter if they login from a 10.7 or 10.8 machine. OS is up to date on both the clients and server.

Has anyone else encountered this weird behavior?
Date modified timestamps resetting on login

Similar Messages

Is there a way to change settings for "date modified" to reflect true file changes instead of changing upon viewing files? This is not just a Word issue.

My team and I open and view files all the time without editing them but the date modified changes anyway. This gets especially troublesome when we are working on files on each others desktops remotely. Is there any way to change these settings to reflect only changes instead of views, moves, and the like? I've read similar posts that have all reference Microsoft products but that is not the case. Our systems here operate in this way regardless of application/file type.

This discussion is going on in another thread where there has been more responses, one fix and a work-around noted. Please go here to read them: https://discussions.apple.com/message/18157324?ac_cid=142432#18157324

To accept all date formats for variables

Hi,
I am getting a vadidation message on refresh of a query on entering European date format in the selection criteria "Please enter value in permitted format for variable XXXX"
I need date to accept all date formats for variables to execute query.
Currently US date format has been accomodated, On entering European date format i get the above validation message.
Please suggest how do i supress this validation message or any other thoughts on the same.
If anyone experienced the same before or applied any notes plz send the SAP Note number for the same. I am currently on BW 3.5.
Message was edited by:
tyson m

tyson,
why dont you control the date display through the user creation / user details option - then your date entries should sort themselves out.
Arun

Get Date Modified for SWF at runtime

This seems like it should be something pretty obvious but I haven't been able to figure out how to get the time stamp (date modified) for the swf that I am in. I want to be able to get the date the swf was published for debugging purposes. Thanks.

you can do that using adobe air, but not for a swf.

Attribute Change Run aborted with an error :Not all data indexed for index

Hi,
I have an issue where the master data Attribute Change Run aborted with an error pointing to the BWA:
Attribute Change Run aborted with an error :Not all data indexed for index
we tried to load only 0 data into it,the error still occured.

Detail message is following:
not all data was indexed for index 'GBP_BIC:XYCH_098('0' for '114')
creation of The BIA INDEX for infocube 'YBC_SD015' terminated while filling

How bad is it to have 4 network mounts for home folders?

I am the tech curriculum guy at a middle school and also manage the servers. I am not an expert at all. Learn enough to make it work efficiently. We got a new server (intel). I am in the process of migrating all the users, groups, home folders and data etc. Had some problems so I called Apple, in my discussion with the tech support there (3-4 hours solving problems) one of the techs questioned my setup. Here is what I used to do:
Server one has all the users in workgroup manager. The home folders for the 6th, 7th and 8th graders are on two separate drive bays on server one. Each grade level folder is a network mount. I then have the faculty home folders on a server two. There is also a shared folder called "Stuff" which mounts for all users and has clipart, movies etc. It is basically a read only mount. The faculty home folders are network mounts of their home folders.
I service between 400 and 500 students a day in the lab, it is quite busy, with anywhere from 60 to 90 users logged on at one time. My thinking last year was that if I could spread out the home folders on different drives, the students wouldn't all be hitting the same drive for saves, data etc. So that one drive wouldn't be spinning its brains out to keep everyone going. That is why I have the 4 network mounts for the home folders. One for each grade level (6,7,8) and the faculty.
My new server has three drives, two of them for home folders. The drives are 750 gb each. He (apple tech) suggested I create a folder in each drive, set it as the network mount and within that folder put two sets of home folders. So, then I would only have two network mounts, but retain my four sets of home folders that would be within the network mounts.
I guess my question is, which is better, to have the 4 network mounts with separate home folder locations on 2 different servers, or consolidate the home folders into 2 network mounts on one server.
He said that the more network mounts, the longer it takes to get computers started up.
Any expert advice here would be greatly appreciated.
Thanks, hope I explained this well enough.
Intel Imac Mac OS X (10.4.8) Lab- Education Intel iMacs - PPC eMacs

I don't think the logins take too long, we may wait 30 seconds or so for the students to login. We have had problems when 60 kids leave and 60 more come in, some login and after the username and password are entered, the login begins then locks. The Apple tech guy thought that could be aggravated by the 4 network mounts. I just sort of thought that with students and teachers accessing 4 different hard drives, that it wouldn't tax one drive as much. I agree that a longer login is a small price to pay for faster working speeds.

Open data set for reading excel file on application server in back ground

open data set for reading excel file on application server in back ground

hi Vijay,
I am afraid you won't be able to read from Excel file on Appl. Server.
ec

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

All Dates displayed for "Characteristic Values" in Query Designer

Hello Experts,
We are on BI 7.0, level 13. I am having an issue within the Query Designer with regards to dates. I have a write-optimized DSO that contains 3 date fields (for example, ZDATE1, ZDATE2, and ZDATE3). Each date InfoObject is of type DATS so the system automatically creates it with reference to 0DATE.
When I create a query in the Query Designer, on the left hand side, I expand the "Characteristic Values" node under each date field. The Query Designer shows the same list of values for each of the 3 dates even though they are not valid values posted in the DSO for those fields.
For example, ZDATE1 only has 1 value posted in the DSO (01/01/2005).
ZDATE2 only has 1 value posted in the DSO (01/01/2006).
ZDATE3 only has 1 value posted in the DSO (01/01/2007).
Bute when I expand the "Characteristic Values" node in the Query Designer, I see ALL THREE values under each date field. I would expect to only see the 1 value posted for the InfoObject in the DSO. Also note that each InfoObject is defined to show "Only posted values in InfoProvider".
It appears that Query Designer will show all values for the reference InfoObject 0DATE instead of the ones posted to the actual InfoObject in the DSO. If I delete the data in the DSO, the Characteristic Values list still remains because they exist in 0DATE. Anyone encounter this before? How can I get the Characteristic Values list to only show posted values for that InfObject?
Thanks for your help!
J

Thanks for the response. I went into the DSO and right clicked on each of the Date fields. I looked at the Provider-specific properties and there is the option for "Query Exec.FilterVal" which only restricts what values appear when restricting during execution, not during query creation.
Is there someplace else I should look or someplace else I can make change to only display posted dates when creating a query? Thanks!

Extract date modified for sorting and renaming

I am new to the area of XMP data so bare with this inquiry..
I am trying to sort a lot of pictures by their actual modified date versus the date modified that shows in the file browser of my os ( mac os x).
Is there a way to extract the actual date modified from within the Description metadata of an image and then use that information to sort and then rename the pictures?
I can see in Adobe Bridge that the data modified is captured and this would actually tell me the correct sequence the pictures should be in. If I had that information I could then sort and determine a renaming scheme to name the sequence and use that in various xml data feeds.
Or is there a way I can access the data through xml. Perhaps through XML I can load the images in order to the resulting file ( in this case a flash movie.)
Thanks in advance for thoughts on this...
Suz

Greetings,
I have produced such a command line tool a long time ago that should do this, I have recently re-released the tools. Even though, the tools are still in BETA stage, you can get them here:
http://www.optimasc.com/products/dex/index.html
Look for the renameto.exe tool in the bin directory after installation.
Please do a backup of your files, since its still BETA!
Good luck!
Carl Eric Codère
http://www.optimasc.com

Any calendar apps that support "date modified" for events?

I would find it very useful if Calendar or a 3rd party calendar program included in the details section of an event, the date added and date modified information. I often make changes to my calendar and then later wonder when I added that change. Or I need to make a change on a repeating event and don't remember if I did it or not. By looking at a date modified, I could tell if I made the change.

Adobe has not made a version of Flash for the iPad.
Kappy explains why. https://discussions.apple.com/message/19446567#19446567
5 Flash Player Alternatives http://www.techshout.com/features/2011/01/flash-player-for-ipad-apps/
 Cheers, Tom

Items "date modified" column when viewing files as list in finder

I'm not really sure if I can change this viewing option, but i will give it a try:
when viewing files as list in finder, "yesterday" items "date modified" column shows up with the term "yesterday", while this does not happen for "today" items, where what shows up is just today's date and not the term "today".
I found this rather confusing, since it is not immediate: i.e. if I want to check for items modified today at a glance, i need to pick today's date from a ist with a number of different dates. As a matter of fact, it's a way easier when checking for yesterday's items.
Suggestions anyone?
Thanks!

toygal wrote:
I am new to Aperature and not very computer savvy so please provide "dummy's guide to" responses.
toygal -- welcome to the Aperture user-to-user forum. iPhoto was designed with you in mind. Aperture is 100x more complicated (and no faster). I strongly recommend that you revert to iPhoto and use it. Compared to Aperture, it will bring you more pleasure and cause you much less frustration. Whoever told you that Aperture is faster not only was wrong, they failed to take into consideration the hours that you would have to practice to become comfortable with it.
Here are some threads which briefly touch on the difference between iPhoto and Aperture -- use the search to find many more.
http://discussions.apple.com/thread.jspa?messageID=13183439&#13183439
http://discussions.apple.com/thread.jspa?messageID=12906017&#12906017
http://discussions.apple.com/thread.jspa?messageID=12901779&#12901779
Message was edited by: Kirby Krieger

Best location for home folders

setting up a new server - with about 150 home folders - and say a maximum of 30 concurrent users:
Does it help to distribute the home folders across 3 or 4 drives?
Will it be faster with external Thunderbolt drives?

Generally yes and yes. The faster the drive(s) the better. Try to predict load to distribute across storage or even servers. Watch for hitting the IOPS wall on your storage if you are dealing with a lot of small files. This has been trouble in a few locations.
But more important than the drive is your connection to the network. Do the simple math. Let's assume you have 1000Base connection and you are supporting wireless clients. The wireless is N and you are able to get about 50Base a connection. This is aggregated into your base stations and the base stations connect at 1000Base to the network. You will likely have multiple points of access. 30 concurrent users are getting the full through put (beginning of session, saves, and end of session) would be 1500Base exceeding the capacity of your access point if all 30 are on the same station.
Now consider the impact if these are wired devices. The more bandwidth you give the server the more requests it can handle as log as the disk array can keep up.
Give your server the fastest network connection you can. Consider bonding to get to 2000Base as that is inexpensive (assuming you have good switches already) and easy to implement. 10GigE is also available but if you don't have the switches already this can be pricey fast.
Be aware of folder redirection (there are some great resources in this forum on how to implement) and also understand the apps that will be used. Not all apps are network home friendly.
Reid
Apple Consultants Network
Author "Yosemite Server – Foundation Services" :: Exclusively available in Apple's iBooks Store
Author "Mavericks Server – Foundation Services" :: Exclusively available in Apple's iBooks Store
Author "Mavericks Server – Control and Collaboration" :: Exclusively available in Apple's iBooks Store

How to change "Date Added" to "Date Modified"in Open a File dialoge

Ever since updating IOS to the latest version the option to sort by "Date Modified" in the open a file dialog has been changed to "Date Added". How can I change this back to "Date Modified"?

Hmm, in OpenSolaris and Solaris Express, the date format is a preference in the Nautilus Preferences dialog. But I don't see it back in JDS 3.
One way (assuming you're using a bash shell) is:
% gnome-session-remove nautilus
% LANG=de_DE nautilus &
which works, but also switches the rest of the nautilus UI into German.
Setting LC_TIME rather than LANG in the second command should work better, because it changes only the dates/times into German. But it still uses the 12 hour clock, with "vorm." and "nachm." instead of "am" and "pm". I suppose that might be considered a bug...

Why folder "Date Modified" doesn't reflect files and subfolders?

Hello.
I have a folder with a "Date Modified" of March 2, 2010.
When I open the folder, I see subfolders and files with more recent dates (...like April 7, 2010).
Isn't the folder "Date Modified" supposed to change with the changing of contents held within the folder?

Hi. So here goes my story. I'm allways keep my MacMini turned on at night. So I work late and re-start working at the day after. And than... voilá: the files I modify are displayed as "Today" modified, instead "Yesterday". During my work, sometime, the file list is refreshed and starts to display the correct date modified. At this middle time, some bizarre lists appears, like a "Today" after "Yesterday" in the list - the order becomes messed as I modify another files.
In my case, webdesign & programming, I use the FTP (Fetch) app to browse local files inside apache's root folder, and Fetch never mess with date modified listing. I's a way out if I'm hurry.
The point is the system is not given high priority to finder's file list as before, becouse this can slow down your mac if there is a lot of windows opened. They should put a refresh button when they made this modification, but those who work in programming knows this thing - fix this bug here, make another one somewhere...

OD 10.8 All dates modified for home folders & files changes on login

Similar Messages

Maybe you are looking for