Setup Assistant cannot write files

corbo angelo -- on Jul. 27 2006

Call me newbie, but I can't find any of the files the setup assistant reports it cannot write to. They are simply missing in action.

I looked for the files below to change permissions, but I can't find any of them on the 6.6.1 download

What am I missing here?

Unable to write to file ./switch.on Unable to write to file ./agents/debug.txt Unable to write to file ./agents/log.txt Unable to write to file ./agents/parameters.include.php Unable to write to file ./articles/ie_bookmarklet.html Unable to write to file ./articles/ie_bookmarklet.reg Unable to write to file ./collections/parameters.include.php Unable to write to file ./feeds/parameters.include.php Unable to write to file ./files/parameters.include.php Unable to write to file ./letters/parameters.include.php Unable to write to file ./scripts/parameters.include.php Unable to write to file ./servers/parameters.include.php Unable to write to file ./services/parameters.include.php Unable to write to file ./shared/hooks.xml Unable to write to file ./shared/hooks.include.php Unable to write to file ./shared/parameters.include.php Unable to write to file ./skins/parameters.include.php Unable to write to file ./users/parameters.include.php

Manufrom Caribbean 2970 posts	on Jul. 27 2006 Maybe you have rights restrictions who doesn't let yacs make files and folders. Did you try with the tgz archive in 6.6.2 version ? Please, verify that your user has the rights with a "chmod -R 766 *" on the yacs path (and subdirectories).
Corbo angelo 2 posts	on Jul. 28 2006 GnapZ: It didn't occurr to me that the installer would create so many files, but it does. I gave all the directories involved write privileges and it stopped complaing. It would be a good idea to include a reminder in the "Installation" section about given proper rights the directories involved. Thanx, adc
Bernard Paquesfrom nearby-an-airport Associate, 8405 posts	inspired from beacon on Aug. 1 2006 Beacon: Glad to see you have been able to move forward afterwards. Actually, the error message reported by YACS is part of pre-installation tests aiming to ensure that YACS has enough rights to proceed. Therefore, I would say that in your case these tests have magnifically worked... Except the feed-back looks maybe too agressive on first installation... Thanks for your interest in YACS, and for your feed-back.