From: oxfordmusic.net <li...@ox...> - 2008-03-13 16:53:13
|
I'm trying to work out why my DomainKeys set up isn't working (I get a BAD response from all the reflectors I've tried). I'm trying to set the DKDEBUG variable so I can see what headers I am signing to compare them to the headers that the reflectors are seeing. I have set DKDEBUG=c (when I do an "echo $DKDEBUG" it shows c), but I can't see any tmp files anywhere. Here's what I did: - set DKDEBUG - killed dk-filter and deleted the .sock - restarted dk-filter - restarted sendmail. Is there something I'm doing wrong? Thanks Andy |
From: Murray S. K. <ms...@se...> - 2008-03-13 16:56:26
|
On Thu, 13 Mar 2008, oxfordmusic.net wrote: > I have set DKDEBUG=c (when I do an "echo $DKDEBUG" it shows c), but I can't > see any tmp files anywhere. They should be in /var/tmp. Are there none there as well? > Here's what I did: > - set DKDEBUG > - killed dk-filter and deleted the .sock > - restarted dk-filter Looks right. > - restarted sendmail. This step wasn't necessary; sendmail doesn't use DKDEBUG. |
From: oxfordmusic.net <li...@ox...> - 2008-03-13 17:07:57
|
> On Thu, 13 Mar 2008, oxfordmusic.net wrote: >> I have set DKDEBUG=c (when I do an "echo $DKDEBUG" it shows c), but I >> can't >> see any tmp files anywhere. > > They should be in /var/tmp. Are there none there as well? There was nothing in there. I tried echo-ing $DK_TMPDIR in case that had been set but it came back empty. I also did a find on all files modified in /var in the last 10 minutes but nothing came up... Andy |
From: Murray S. K. <ms...@se...> - 2008-03-13 17:16:30
|
On Thu, 13 Mar 2008, oxfordmusic.net wrote: >> They should be in /var/tmp. Are there none there as well? > > There was nothing in there. I tried echo-ing $DK_TMPDIR in case that had > been set but it came back empty. I also did a find on all files modified > in /var in the last 10 minutes but nothing came up... I just tried it with the 0.6.0 code on my home system and it created the files just fine, both for signing and verifying. Are the permissions on /var/tmp appropriate (i.e. mode 1777)? |
From: oxfordmusic.net <li...@ox...> - 2008-03-13 17:40:21
|
>>> They should be in /var/tmp. Are there none there as well? >> >> There was nothing in there. I tried echo-ing $DK_TMPDIR in case that had >> been set but it came back empty. I also did a find on all files modified >> in /var in the last 10 minutes but nothing came up... > > I just tried it with the 0.6.0 code on my home system and it created the > files just fine, both for signing and verifying. > > Are the permissions on /var/tmp appropriate (i.e. mode 1777)? > [root@botley libdk]# ls -all /var/tmp/ total 16 drwxrwxrwt 2 root root 4096 Jan 28 11:12 . drwxr-xr-x 23 root root 4096 Oct 1 10:56 .. Andy |
From: Murray S. K. <ms...@se...> - 2008-03-13 17:42:30
|
On Thu, 13 Mar 2008, oxfordmusic.net wrote: >> Are the permissions on /var/tmp appropriate (i.e. mode 1777)? > > [root@botley libdk]# ls -all /var/tmp/ > total 16 > drwxrwxrwt 2 root root 4096 Jan 28 11:12 . > drwxr-xr-x 23 root root 4096 Oct 1 10:56 .. It should be creating the files then, for signing and for verifying signed messages. The fact that it isn't means either DKDEBUG isn't actually set in the environment (maybe you just set it as a shell variable?) or the attempt to open a file in /var/tmp is failing. You'd have to go in with the debugger to figure out which is true. Are you familiar with how to do that? |
From: oxfordmusic.net <li...@ox...> - 2008-03-13 17:54:00
|
> > It should be creating the files then, for signing and for verifying signed > messages. The fact that it isn't means either DKDEBUG isn't actually set > in the environment (maybe you just set it as a shell variable?) or the > attempt to open a file in /var/tmp is failing. > > You'd have to go in with the debugger to figure out which is true. Are > you familiar with how to do that? > Not vastly experienced in the ways of *nix command lines! The debugger option scares me. The first option, however, may well be what's happening. Here's what I did to set the variable: [root] DEBUG=c [root] export $DEBUG Does that mean I've set it as a shell variable? I'm using Bash and don't seem to have setenv in my path. Andy |
From: Murray S. K. <ms...@se...> - 2008-03-13 18:10:21
|
On Thu, 13 Mar 2008, oxfordmusic.net wrote: > Not vastly experienced in the ways of *nix command lines! The debugger > option scares me. The first option, however, may well be what's happening. > Here's what I did to set the variable: > [root] DEBUG=c > [root] export $DEBUG > > Does that mean I've set it as a shell variable? I'm using Bash and don't > seem to have setenv in my path. Try: DKDEBUG=c;export DKDEBUG ...i.e. leave out the "$". |