#13 jobs killed with error

closed-out-of-date
None
8
2001-05-11
2001-04-25
No

Hello !

I translated and installed queue 1.30.1 with the
following configure options:
./configure --prefix=/opt/queue-1.30.1
--sharedstatedir=/common/run/data/queued --enable-root
--datadir=/common/run/data/queued/share
--localstatedir=/var/queue

before that i modified configure like suggeted to:
QUEUEDIR=\"`eval echo ${sharedstatedir}/queue`\"

The queued looks for now in
/common/run/data/queued/queue/now
but it looks for mail_log2 in
/common/run/data/queued/var/queue/now
So i made a link.
Which permssions should this directory have ?
currently it is 700 for root.

The error-message when aboting the job is:
Can't unlink(now/CFDIR/cfm778893818): No such file or
directory

with various numbers.

Is Makefile.in also used when I not use autoconf
automake etc. ?

The Machines running queue are Sun U60 with Solaris
2.5.1, 7 and 8.

Thank you for any hint.

Christian

Discussion

  • Christian Parg

    Christian Parg - 2001-04-25
    • priority: 5 --> 8
     
  • Christian Parg

    Christian Parg - 2001-05-03

    Logged In: YES
    user_id=177130

    Hello !
    In the meantime I tried the queue-developement
    cvs version of 2nd may 2001.
    The profiles file is still installed under localstatedir
    is this intended ?
    In that case it has to be maintained on each host, or am I
    wrong ?
    Maybe the configure-stuff etc. was not uptodate !?
    Comments?

    Regards,
    Christian

     
  • Werner G Krebs

    Werner G Krebs - 2001-05-11
    • assigned_to: nobody --> wkrebs
    • status: open --> closed-out-of-date
     
  • Werner G Krebs

    Werner G Krebs - 2001-05-11

    Logged In: YES
    user_id=32209

    Please upgrade to the latest version, which is a major upgrade and see if you still have the problem.

    1.40.1 is out in beta, or use the CVS version. Thank you.

    It may also depend whether you are running this in single user or root-wide installation. It sounds like you
    are doing root-wide installation. However, if you are doing single-user, then permission should be set to that
    user (not root.) I suspect 1.40.1 has fixed the problem, but maybe not.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks