Package: ejabberd
Version: 2.1.10-4+deb7u1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

we use mod_muc_log : 

{mod_muc_log,[
       {allow_room_log,true},
        {access_log,muc},
        {outdir,"/XXXXXXXXXXXXXX/muclogs"},
        {dirtype,plain},
       {timezone,local},
        {top_link,{"httpXXXXXXXXXXXXXXXXXXXXXXXXx/conferences/"}},
        {cssfile,false}
        ]},

exerpt of lsof -n |grep jabber :

beam       7079         ejabberd  538w      REG              144,7     13101    
 969706 /XXXX/m...@xxx.com/2014-03-28.html
beam       7079         ejabberd  539w      REG              144,7      2707    
2436415 /XXXX/t...@xxx.com/2014-03-26.html
beam       7079         ejabberd  540w      REG              144,7      4931    
1362816 /XXXX/p...@xxx.com/2014-03-26.html
beam       7079         ejabberd  541w      REG              144,7      2709    
 969710 /XXXX/m...@xxx.com/2014-03-30.html
beam       7079         ejabberd  542w      REG              144,7     19441    
1650181 /XXXX/d...@xxx.com/2014-03-28.html
beam       7079         ejabberd  543w      REG              144,7      4613    
2672194 /XXXX/v...@xxx.com/2014-03-26.html
beam       7079         ejabberd  544w      REG              144,7     15022    
1650179 /XXXX/d...@xxx.com/2014-03-27.html
beam       7079         ejabberd  545w      REG              144,7      5875    
2467330 /XXXX/l...@xxx.com/2014-03-28.html
beam       7079         ejabberd  546w      REG              144,7      4425    
3792974 /XXXX/s...@xxx.com/2014-03-28.html
beam       7079         ejabberd  547w      REG              144,7      5197    
2690287 /XXXX/s...@xxx.com/2014-03-28.html
beam       7079         ejabberd  548w      REG              144,7     20011    
3378224 /XXXX/w...@xxx.com/2014-03-28.html
beam       7079         ejabberd  549w      REG              144,7     10268    
1362820 /XXXX/q...@xxx.com/2014-03-28.html
beam       7079         ejabberd  550w      REG              144,7     10447    
6135881 /XXXX/t...@xxx.com/2014-03-28.html
beam       7079         ejabberd  551w      REG              144,7      4300    
2426811 /XXXX/n...@xxx.com/2014-03-26.html
beam       7079         ejabberd  552w      REG              144,7      3656    
2690286 /XXXX/s...@xxx.com/2014-03-27.html
beam       7079         ejabberd  553w      REG              144,7     12378    
2501195 /XXXX/r...@xxx.com/2014-03-28.html




   * What exactly did you do (or not do) that was effective (or
     ineffective)?

restarting the server jabber every month is closing the logs


   * What outcome did you expect instead?


I expect jabber server to close its muc logs at the end of the day.

*** End of the template - remove these lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (449, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to