probably because the files in that directory are tied to another user than the one of your session.
It often is the case if you have handled those files via FTP.
The ftp user is not the same than the shell user.
Check that, with a "ls -lah" on the files in that folder, and the result if "id".
"id" will give you the username and id and the main group name and id of your user.
"ls -lah" will show you the name and group of the files.
For example:
Code:
tmo@NAS:~$ id
uid=1000(tmo) gid=407(webdev) groups=7(lp),9(kmem),10(wheel),18(audio),19(cdrom),27(video),35(games),70(postgres),80(cdrw),85(usb),100(users),407(webdev),1004(plugdev),1010(vboxusers),1011(scanner),1013(uinput),1014(tuntap),1022(realtime),1023(pulse-access),1024(pulse),1029(svnusers)
This tells me that I am logged with the user "tmo", and the main group is "webdev"
and this:
Code:
tmo@NAS:~$ ls -lah
-rwxr-xr-x 1 apache webdev 281 Jul 31 2008 stopVnc.sh
tells that the file stopVnc is owned by the user "apache", in the same ggroup as me.
If the user and/or group are different, and that the user or group permission don't give you write permissions to the file, you will have this prompt.
So, if you are sure of yourself, as this could means "no more ftp working", you can change the owner of the files in your directory with:
Code:
chown -R myUser:myGroup theDirectory
After that, you should not have any prompt.