John Asher <[log in to unmask]> writes: > [...] would it not be easier altogether if the system administrator > kept a record of who owns which lists and simply charges using the > fact that all files associated with a list are called LISTNAME.* This would work too, for list archive files. It doesn't seem much simpler though and I can see two disadvantages: 1) a list might have other files associated with it that didn't follow the LISTNAME.* naming pattern. If they were all in a particular directory, they'd still be caught. 2) using the scheme you're proposing would require that a list be updated for the script every time a new list were created. If the files were kept under a directory that was named according to the user who owns the list (i.e. /home/listserv/notebook/naleks for my lists) then the script never needs to be changed. -- Norm A Catholic, a Jew, an African-American, and a Gay all walk into a bar. The bartender looks up at them and says, "What is this, a joke?"