This error also occurs in the latest version for Sarge (from t-p-u).

I noticed this error when I had to set the setuid bit again after updating 
from version 3.2.2-2 to version 3.2.2-2.sarge1.

Reply via email to