#100 closed enhancement (invalid)

expire inative users

Reported by: mauritz@… Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.0.1
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


Hello guys,

What do you think about expire users who not use the service for a long time? exemple: 100 days

[]'s Mauritz

Attachments (0)

Change History (7)

comment:1 Changed at 2006-02-13T12:41:39Z by timing

Define 'users who do not use the service for a long time' I mean, if I recieve messages, but do not reply to them, will I be disconnected? And if I was a user on this network, I would create an automated help message in &bitlbee everyday.

comment:2 Changed at 2006-02-13T12:49:36Z by wilmer

Resolution: fixed
Status: newclosed

Timing, I think this is about clearing account files of users that didn't log in for a longer time. Which can be done with a nice find command line. See "man find" for more information, it's how I do it on the public servers from time to time.

Something like this, for example:

$ find . -mtime +90 | xargs rm

comment:3 Changed at 2006-02-13T12:49:51Z by admin

Resolution: fixed
Status: closedreopened

comment:4 Changed at 2006-02-13T12:50:16Z by admin

Resolution: invalid
Status: reopenedclosed

It's not a bug. :-)

comment:5 Changed at 2006-02-13T16:51:27Z by mauritz@…

Resolution: invalid
Status: closedreopened

This is a user who use my server every day: -rw------- 1 root wheel 298 Jul 20 2005 KurtKraut.accounts -rw------- 1 root wheel 1211 Jul 20 2005 KurtKraut.nicks

So, these files only change date when he change or set accounts.. Not register the last login.

comment:6 Changed at 2006-02-13T20:44:45Z by timing

okay, so maybe bitlbee needs to touch a file now and then, just for fun

comment:7 Changed at 2006-02-13T20:49:33Z by wilmer

Resolution: invalid
Status: reopenedclosed

Hmm, then he disabled auto-save. I wonder why. With BitlBee <0.8 (or something similar, don't know when the account command appeared exactly) that made sense, but I don't see why people would want that these days.

Anyway, checking atime is another possibility, but .accounts files don't have very accurate atimes because BitlBee touches them too when people *try* to log in (but use the wrong password), which does seem to happen on public servers sometimes. So then after you'd have to clean up .accounts files when the .nicks file disappears.

Anyway, this is a little Unix shell scripting exercise, nothing for BitlBee. Have fun. ;-)

(Invalid might maybe not be a very suitable "resolution", maybe I should add a "notabug" resolution to the list of possibilities...)

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.