Bug#321383: no access to /var/run/bcron-spool, crontab -l won't work

2005-08-05 Thread Tommi Virtanen
Package: bcron
Version: 0.09-1
Severity: important

crontab -l etc. won't work on a normal install, thus making most of the
package not work without manual fixing (thus severity important).

[1 [EMAIL PROTECTED] ~]$ crontab -l
bcrontab: Fatal: Could not connect to bcron-spool: Permission denied
[111 [EMAIL PROTECTED] ~]$ ls -ld /var/run/bcron-spool
drwx--  2 root root 1024 2005-08-05 10:15 /var/run/bcron-spool/
[0 [EMAIL PROTECTED] ~]$


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



Bug#321383: no access to /var/run/bcron-spool, crontab -l won't work

2005-08-05 Thread Tommi Virtanen
Oops, I just noticed /var/run/bcron-spool isn't the real socket,
the socket is .bcron-spool. This works:

BCRON_SOCKET=/var/run/.bcron-spool bcrontab -l

Still, the default configuration is broken.


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



Bug#321383: no access to /var/run/bcron-spool, crontab -l won't work

2005-08-05 Thread Gerrit Pape
On Fri, Aug 05, 2005 at 10:42:46AM +0300, Tommi Virtanen wrote:
 Oops, I just noticed /var/run/bcron-spool isn't the real socket,
 the socket is .bcron-spool. This works:
 
 BCRON_SOCKET=/var/run/.bcron-spool bcrontab -l
 
 Still, the default configuration is broken.

Yes, this was due to the change from 0.08 to 0.09, upstream adopted the
new path to the socket (previously in /tmp/), and I didn't test
properly.

Thanks for the report, Gerrit.
Index: bcron.h
===
RCS file: /cvs/bcron/bcron.h,v
retrieving revision 1.2
diff -u -r1.2 bcron.h
--- bcron.h 20 Jul 2005 13:00:31 -  1.2
+++ bcron.h 5 Aug 2005 08:01:32 -
@@ -8,7 +8,7 @@
 
 #define BCRON_SPOOL /var/spool/cron
 #define CRONTAB_DIR crontabs
-#define SOCKET_PATH /var/run/bcron-spool
+#define SOCKET_PATH /var/run/.bcron-spool
 #define BCRON_USER cron
 #define TRIGGER trigger