I went ahead and deleted the directory that was giving the errors, and when
cron ran again, I got the same error -- except with the directory in the
next sequential order. Looks like something is wrong with more than just
that one directory.
I checked the permissions and all the files are owned by vpopmail with group
vchkpw. All the directories have 700 permissions and the files in them have
600.
The /var/cache/sqwebmail directory itself is owned by vpopmail with group
root and has 755 permissions.
Trey Nolen
[EMAIL PROTECTED]
> > Trey Nolen writes:
> >
> > > The entire message was at the bottom of my email. I forwarded the
> > You received an answer the first time you asked this: try actually
looking
> > at that file or directory, and see what's in there.
> >
> > You'll need to provide this additional information.
> >
>
> I appologize if this has been answered before. I never saw the email.
> Anyway, to answer your query, the 137856 is a directory. In that directory
> are two entries: jm and ri which are both directories.
> In each directory is a file in the form of <emailaddress>.authvchkpw
> For example, the jm one has [EMAIL PROTECTED]
> In that file is:
> 89 89 /home/vpopmail/domains/domain.com/jmoore/Maildir
> [EMAIL PROTECTED]
> AUTHFULLNAME=jmoore
>
> The ri directory contains an almost identical file -- just with a
different
> email address.
>
> In the /var/cache/sqwebmail directory there are several of these numbered
> directories. Each has similar entries (some have just one entry). None of
> these other directories cause the cron error, though.
>
> Would it be OK to just delete the offending directory? After all, this is
> just cache, and the info just wouldn't be found in cache, right?
>
> Trey Nolen
> [EMAIL PROTECTED]
>
> > >
> > > Trey Nolen
> > > [EMAIL PROTECTED]
> > >
> > >
> > > On Thu, 9 Aug 2001, Mike Rogers wrote:
> > >
> > >> You sure it's not reporting that it is doing it? Cron logs every
> event, and
> > >> when it happens every few minutes, it will go and log every single
> event.
> > >> What is the actual error message? That would mostlikely be most
> helpful in
> > >> fixing it
> > >> --
> > >> Mike
> > >>
> > >> ----- Original Message -----
> > >> From: "Trey Nolen" <[EMAIL PROTECTED]>
> > >> To: <[EMAIL PROTECTED]>
> > >> Sent: Thursday, August 09, 2001 9:07 AM
> > >> Subject: Fw: Cron <root@mail> /bin/su -c
> > >> "/usr/local/share/sqwebmail/cleancache.pl" bin
> > >>
> > >>
> > >> > I posted this a whle back, but didn't get any responses. I thought
> I'd
> > >> post
> > >> > it again to see if anyone has any ideas. Everything *SEEMS* to be
> working
> > >> > OK, except that I get the message below from cron all the time. It
> is
> > >> > always the exact same error. Does anyone know if this is something
> to be
> > >> > concerned about? This is sqwebmail 2.1.1 on a Debian system.
> > >> >
> > >> > Thanks for any help!
> > >> >
> > >> > Trey Nolen
> > >> > [EMAIL PROTECTED]
> > >> >
> > >> > ----- Original Message -----
> > >> > From: Cron Daemon <root@mail>
> > >> > To: <root@mail
> > >> > Sent: Thursday, August 09, 2001 8:05 AM
> > >> > Subject: Cron <root@mail> /bin/su -c
> > >> > "/usr/local/share/sqwebmail/cleancache.pl" bin
> > >> >
> > >> >
> > >> > > /var/cache/sqwebmail/137856: Illegal seek
> > >> > >
> > >> >
> > >> >
> > >>
> > >
> >
> >
> >
> > --
> > Sam
> >
> >
>
