Bug#284788: [Logcheck-devel] Bug#284788: logcheck: Installs cron.d file before creating user causing cron to complain

[Jefferson Cowart]

It's an old box that I use for packet sniffing/low scale IDS. I also gave
you the output of cpuid. Just running those two command caused the system
load to jump to 0.13 so I suspect that simply running apt-get to install
logcheck would have pushed it relatively high.

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : CyrixInstead
cpu family      : 5
model           : 7
model name      : Cyrix MediaGXtm MMXtm Enhanced
stepping        : 2
cpu MHz         : 0.000
cache size      : 16 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu tsc msr cx8 cmov mmx cxmmx
bogomips        : 88.06

$ cpuid
 eax in    eax      ebx      ecx      edx
00000000 00000002 69727943 64616574 736e4978
00000001 00000540 00000000 00000000 00808131
00000002 00007001 00000000 00000000 00000080
80000000 80000005 00000000 00000000 00000000
80000001 00000540 00000000 00000000 01818131
80000002 69727943 654d2078 47616964 206d7458
80000003 74584d4d 6e45206d 636e6168 00006465
80000004 00000000 00000000 00000000 00000000
80000005 00000000 00007001 00000080 00000000

Vendor ID: "CyrixInstead"; CPUID level 2

Cyrix-specific functions
eax in: 0x80000000, eax = 80000005 ebx = 00000000 ecx = 00000000 edx =
00000000
eax in: 0x80000001, eax = 00000540 ebx = 00000000 ecx = 00000000 edx =
01818131
eax in: 0x80000002, eax = 69727943 ebx = 654d2078 ecx = 47616964 edx =
206d7458
eax in: 0x80000003, eax = 74584d4d ebx = 6e45206d ecx = 636e6168 edx =
00006465
eax in: 0x80000004, eax = 00000000 ebx = 00000000 ecx = 00000000 edx =
00000000
eax in: 0x80000005, eax = 00000000 ebx = 00007001 ecx = 00000080 edx =
00000000
Family: 5 Model: 4 [BXm]

FPU   Floating Point Unit
Time Stamp Counter
RDMSR/WRMSR (Model Specific Registers)
COMPXCHG8B Instruction
CMOV  Conditional Move Instruction
MMX instructions
TLB: 32 entries 4-way associative 4KB pages
L1 Cache: 16KB 4-way associative 16 bytes/line

Extended info:
Family: 5 Model: 4 [6x86/GXm]

Extended feature flags:
FPU   Floating Point Unit
Time Stamp Counter
Cyrix MSR
COMPXCHG8B
CMOV
FPU CMOV
MMX
Extended MMX

Processor name string: Cyrix MediaGXtm MMXtm EnhancedTLB: 32 entries 4-way
associative 4KB pages
L1 Cache: 16KB 4-way associative 16 bytes/line


----------------
Thanks
Jefferson Cowart
Jeff at cowart.net   

> -----Original Message-----
> From: maximilian attems [mailto:max at stro.at] On Behalf Of maks attems
> Sent: Friday, December 10, 2004 01:59
> To: Jefferson Cowart; 284788 at bugs.debian.org
> Subject: Re: [Logcheck-devel] Bug#284788: logcheck: Installs 
> cron.d file before creating user causing cron to complain
> 
> On Wed, 08 Dec 2004, Jefferson Cowart wrote:
> 
> > After installing logcheck on my system last night I did not 
> recieve any
> > reports. Upon checking the logs I found that the logcheck 
> file had been
> > copied into /etc/cron.d before adduser had been run. Cron 
> picked up the
> > new file and then complained that the user was invalid. Relevant log
> > lines below. I just restarted cron which I believe has 
> fixed the issue.
> > Perhaps this can be fixed by copying the file in postinst 
> after the user
> > has been created.
> > 
> > auth.log:Dec  8 03:27:13 JeffDebian2 groupadd[2153]: new group:
> > name=logcheck, gid=106
> > auth.log:Dec  8 03:27:13 JeffDebian2 useradd[2154]: new user:
> > name=logcheck, uid=106, gid=106, home=/var/lib/logcheck,
> > shell=/bin/false
> > auth.log:Dec  8 03:27:15 JeffDebian2 gpasswd[2158]: set 
> members of adm
> > to logcheck
> > syslog:Dec  8 03:27:01 JeffDebian2 cron[878]: Error: bad 
> username; while
> > reading /etc/cron.d/logcheck
> > syslog:Dec  8 03:27:01 JeffDebian2 cron[878]: Error: bad 
> username; while
> > reading /etc/cron.d/logcheck
>  
> indeed that's bad timing.
> i could only reproduce it with a SIGSTOP in the "Setting up logcheck".
> 
> what's your box? (cat /proc/cpuinfo) 
> was it under heavy io while installing logcheck?
> 
> thanks for giving as more clues.
>  
> --
> maks
> 
>