Jean Charles Delepine wrote:
Raphael Hertzog <[EMAIL PROTECTED]> écrivait (wrote) :
On Thu, 21 Dec 2006, Jean Charles Delepine wrote:
Package: sympa
Version: 5.2.3-0.5
Severity: wishlist
Tags: patch
While installing sympa with /var/lib/sympa/ imported from an netapp :
Installing new version of config file /etc/logrotate.d/sympa ...
chown: changing ownership of `/var/lib/sympa/.snapshot': Read-only
file system
One solution is to ignore chown and chmod exit value :
I don't think it's a good idea to ignore such failures! The installation
rightfully fails if it can't set the proper modes/owners.
Afte a failure you remount your netapp rw, and restart the install...
What specific use case do you have ?
On an netapp .snapshot/ is read-only, but only .snapshot.
So we just need to exclude "hidden" files from ch* operation ?
I can't think of a failure on chmod/chown which should'nt have make the
install crash before in the process. By not crashing here we let the
install finish, databese, web server, and the admin will have clear
error logs if sympa can't start.
Disk failures can happen at any time and only to certain files,
so they should reported immediately.
Bye
Racke
--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
