Hi

Most of them have reason 'operation not supported'.

It is the following vserver kernel syscall that return this information:

    /** \brief   Returns information about attributes and assigned context of a 
file.
     *  \ingroup syscalls
     *
     *  This function returns the VC_IATTR_XXX flags and about the assigned
     *  context of a file. To request an information, the appropriate bit in
     *  \c mask must be set and the corresponding parameter (\a xid or \a
     *  flags) must not be NULL.
     *
     *  E.g. to receive the assigned context, the \c VC_IATTR_XID bit must be
     *  set in \a mask, and \a xid must point to valid memory.
     *
     *  Possible flags are \c VC_IATTR_ADMIN, \c VC_IATTR_WATCH , \c 
VC_IATTR_HIDE,
     *  \c VC_IATTR_BARRIER, \c VC_IATTR_IUNLINK and \c VC_IATTR_IMMUTABLE.
     *
     *  \param filename  The name of the file whose attributes shall be 
determined.

     *  \param xid       When non-zero and the VC_IATTR_XID bit is set in \a 
mask,
     *                   the assigned context of \a filename will be stored 
there.
     *  \param flags     When non-zero, a bitmask of current attributes will be
     *                   stored there. These attributes must be requested 
explicitly
     *                   by setting the appropriate bit in \a mask
     *  \param mask      Points to a bitmask which tells which attributes shall 
be
     *                   determined. On return, it will masquerade the 
attributes
     *                   which were determined.
     *
     *  \pre  mask!=0 && !((*mask&VC_IATTR_XID) && xid==0) && 
!((*mask&~VC_IATTR_XID) && flags==0) */
  int           vc_get_iattr(char const *filename, xid_t * /[EMAIL 
PROTECTED]@*/ xid,
                             uint_least32_t * /[EMAIL PROTECTED]@*/ flags,
                             uint_least32_t * /[EMAIL PROTECTED]@*/ mask) 
VC_ATTR_NONNULL((1));

According to the code it either:
* Return -1
* Stored mask is != flags requested.
  The requested flags are VC_IATTR_IUNLINK and VC_IATTR_IMMUTABLE.

So I think you have a kernel problem here.

Regards,

// Ola

On Sun, Dec 17, 2006 at 07:09:51PM +0100, Daniel Dehennin wrote:
> Le 4855 Septembre 1993, Ola Lundqvist a tapoté:
> > Can it be related to that we use beecrypt6 instead of beecrypt2...?
> > Probably not but maybe.
> 
> I don't know.
> 
> > Can you increase the verbosity and send me the output?
> >
> > vhashify -v -v -v -v -v -v 
> >
> > (-v 6 times).
> >
> > With that you can see the reason for skipping for each file.
> 
> Ok, see attached file.
> -- 
> Daniel 'NebuchadnezzaR' Dehennin
> Récupérer ma clef GPG:
> gpg --keyserver pgp.mit.edu --recv-keys 0x2A408F69
> 



-- 
 --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ----
/  [EMAIL PROTECTED]                   Annebergsslingan 37        \
|  [EMAIL PROTECTED]                   654 65 KARLSTAD            |
|  http://opalsys.net/               Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to