1 $Id: TODO,v 1.31 1999-04-29 09:37:45 ivan Exp $
3 If you are interested in helping with any of these, please join the mailing
4 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid
9 > Second, when trying to add a new user I get two types of errors; first one
10 > is when I place an e-mail address and select the "submit," Freeside
11 > complains with "Error: Unknown local account (specified literally)"
13 You probably put a (local) email address in for email invoices. Freeside
14 stores these as references to the database records, so (for example) they
15 follow username changes.
17 I'm guessing you put in the email address that you were creating, and got
18 that error because it didn't exist yet. Sounds like a buglet to me. I'll
19 try to fix that soon; in the meantime you can add the invoicing email
22 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
23 and use the numeric types, which *finally* work right.
24 On Sat, Apr 24, 1999 at 12:52:00PM -0700, Mr. Poet wrote:
26 > Error creating cust_bill record: ERROR: parser:
27 > attribute 'charged' is of type 'money' but expression
28 > is of type 'float8' You will need to rewrite or cast
29 > the expression ! Check updated but unbilled packages
32 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
33 and use the numeric types, which *finally* work right (well, according to
34 the web site, anyway).
36 In the mean-time, this could probably be fixed with the reverse of
37 the kludge in FS::Record::new. This removes `$' and `,' from money fields
38 coming out of the database. Something which fixed up the data so Postgres
39 was happy with it could go in FS::Record::_quote, for data going into the
42 our data display problem might be a Freeside problem wrt not using
43 Oracle-compatible DBI syntax (uses the return value from $sth->execute as
44 a number of rows). Fixing this is on the TODO.
46 hooks for arbitrary commands out of configuration files
47 svc_acct.pm svc_acct_sm.pm etc.
49 Add this to a FAQ, along with doing it for middle names:
52 > What I'm finding difficult is how to easily
53 > customize fields. For example, I am trying to add a "middle name" field
54 > to the Customer Edit, view, etc. If I'm going about it right, it appears
55 > I have to edit the cust_main.cgi under edit and edit/process and the
56 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
57 > some light on the best way of doing this.
59 You have the basic idea. To implement that completely, I would:
60 - Add the new field to bin/fs-setup for new users
61 - Document the field in htdocs/docs/schema.html
62 - Document the change in a new file, htdocs/docs/upgrade4.html
63 * Run bin/dbdef-create
64 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
66 For bonus points, I'd grep around for the various bits which use "$first
67 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
68 , like search/cust_main.cgi
70 document security model:
71 Don't forget about Apache usernames - since, via the mapsecrets file, each
72 user can login to the SQL database with a different username and
73 password, you can utitilize the security model of the SQL database as
74 well. Also, each username here can point to a different configuration
75 directory where you could store user-specific configuration info. Then
76 you could link each username to one-to-many agents.
77 (The web demo works using a trivial version of this.)
79 Yes, queue processing or the equivalent via checkpoint fields on various
80 talbes (which you pick up via a pretty simple SELECT) would be really
83 default (and ordering) state/county/country config file
85 cust_main_county table to provide a preferred ordering, so the most common
86 entries would be at the top of the selection box. automatically, based on
89 hmm... maybe svc_acct__shell should check off the legal shells list if
90 applicable? yeah... cool.
92 payinfo field should me much larger than 16
95 [Mon Apr 12 20:31:21 1999] [error] [Mon Apr 12 20:31:21 1999] null: Error closing true: Broken pipe at /usr/local/lib/site_perl/FS/cust_main.pm line 615.
97 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
98 (view/cust_pkg and view/svc_*)
100 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
101 (all the actual date handling uses UNIX timestamps and is fine)
103 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
106 one-time/per-customer/? changes in rates and descriptions ('remembered
107 invoices'): implement by creating a new package on the fly... but it isn't
108 associated with any agent types so it won't show up for other customers to buy.
109 (but also... make sure they go away when the customer does! - need this? :
110 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
111 with custnum and partpkg (like type_pkgs)
112 (what happens if you hit "custom pricing" but the pricing is already custom?)
114 Lay out any remaining ugly forms better.
116 remove "records identical" warning? gets in the way of more important stuff.
117 or fix logic which tries to update identical records??
118 1.2 should be quiet enough that the error log is useful, hopefully.
120 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
121 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
122 (22 characters!) It seems that stuff over the limit is silently ignored,
123 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
124 stock Postgres. see rfc2138 for what's affected
125 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
126 (mysql has a 64 character max column length. others?)
128 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
129 (when sending mail in cust_main.pm::bill or svc_domain.pm)
131 look at DBIx::Recordset! (and Tie::DBI, and...)
133 undefined conf/lpr gives this uninfomative error:
134 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
136 l5/site_perl/FS/cust_main.pm line 629.
137 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
139 l5/site_perl/FS/cust_main.pm line 631.
140 So give a meaningful error!
142 password and slipip stuff in svc_acct.pm store need to be split into two fields or something, so the silliness in svc_acct.pm and svc_acct.export with looking at the data to decide what to do with it can be fixed
144 i10n: Apache::Language
146 Apache::Session? Other useful Apache::* ?
148 email invoices are only sent for the BILL payby. If setup, should statements
149 (since they're not invoices) be sent for COMP and CARD as well?
151 $cgi->keywords is causing the (hard to trace) error:
152 Use of uninitialized value at (eval 5) line 5
154 edit/cust_main.cgi gives an uninformative error message:
155 > Can't call method "agentnum" without a package or object reference at
156 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
157 if there are no agents.
159 (is this missing on any web screens? (easy with $cust_svc->label)
160 Add the ability for services to filter information up to the package level
161 for web screens, so you can select a particlar package based
162 on username or domain name, etc.
164 Allow a cancelled/suspended/active status from packages to bubble up to
165 the customer lists. Put active, then suspended, then cancelled accounts.
166 Similar ordering on the package listing inside a single customer.
168 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
169 the web interface in general needs to be redone in a more abstract way.
171 false laziness: some of search/svc_acct_sm.cgi was copied to search/svc_domain.cgi. but web interface in general needs to be rewritten in a mucho cleaner way.
173 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
175 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
177 add a select method to FS::Record?
179 one-time/per-customer/? changes in rates and descriptions ('remembered
180 invoices'): implement by creating a new package on the fly... but it isn't
181 associated with any agent types so it won't show up for other customers to buy.
182 (but also... make sure they go away when the customer does! - need this? :
183 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
184 with custnum and partpkg (like type_pkgs)
185 (what happens if you hit "custom pricing" but the pricing is already custom?)
187 You can't delete the stuff under administration yet. Add this,
188 _including_ making sure the thing you are deleting is not in use!
190 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
192 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
193 loading of configuration. (pry need same idea, but will run immediately if
194 context allows). Looks like error is masked by 'use FS::cust_svc' which in
195 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
198 Allow a cancelled/suspended/active status from packages to bubble up to
199 the customer lists. Put active, then suspended, then cancelled accounts.
200 Similar ordering on the package listing inside a single customer.
202 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
205 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
207 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
209 .us domains and others!
210 site_perl/svc_domain.cgi (hmm... or maybe should have a button? or maybe svc_domain.pm should handle this) should set $whois_hack for non-internic domains, so you can add them...
212 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
213 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
215 (test cust_main.pm with cybercash v2 and v3, especially with the callback
216 stuff AND with mod_perl w/cybercash v2 kludge in package main)
217 (callback stuff should be eliminated by now)
219 bah, table/itable/*table in FS::CGI is silly.
221 doc Apache::AuthDBI as well
223 Provide sample httpd.conf files.
225 hey look: Tie::DBI! Check that out. Override its commit with something that
226 does perl-side caching for ? a performance improvement and as an emulation
227 layer to plug in f.ex mysql's atomic transactions
229 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
230 Fix it anyway unless we migrate to Tie::DBI.
234 cust_bill.pm uses '==' comparison on dates because they're currently ints
236 config file for allowed card types
238 write instructions for adding new services w/svc_Common.pm. Get rid of all
239 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
242 test and document libapache-dbi-logger (woo!)
244 radius logfile parsing and perl expression check.
246 Fix in cust_bill BUGS:
247 There is an off-by-one error in print_text which causes a visual error (Page 1
248 of 2 printed on some single-page invoices).
250 fields should be a method against a FS::Record or derived object, as well as
251 being something you can call as FS::Record::fields('tablename'). Might
252 even be able to handle both in the same routine (that would be neato).
254 Immediate removal of incorrectly entered check payments (can't take too
255 long to do this, or accounting is fubared).
257 Add code to move from one service to another (POP to SLIP/PPP, etc.).
258 This _should_ be possible by working off the rules in part_svc rather than
259 hardcoding anything in. The rules in part_svc may need some elaboration,
262 Use ut_ FS::Record methods in all derived classes (possibly some from dbdef?... eventually all from dbdef??? - but then `dbdef-create' would be impossible as there would be metadata we couldn't ask the backend for. hmm.)
264 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
265 Expand the HylaFAX interface (also possibly generalize for other fax
266 softwar ie .comfaxe); allow things like arbitrary faxes of sales
267 literature, specific troubleshooting documents and so on. Maybe even
268 allow users to do this (though that might not belong in Freeside).
270 misc/process/sendconfig.cgi
271 Configure fax recipients via a separate box rather than using the finger
272 name or first+last from cust_main.
274 move all phone number logic out of Freeside - let HylaFAX or whatever
277 soundex searches for customer name and company? where are free soundex tools? (standard Text::Soundex duh) - I could have sworn I saw Text::Soundex on CPAN?!
279 should be able to link on some field in email alias (right now you can link
280 on username or domain with a fallback to svcnum)
282 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
284 deleting an svc_domain should delete all associated svc_acct_sm records.
285 same with a svc_acct.
287 periodic password encrypter
289 Automated, configurable notification, suspension and cancellation of
294 Allow for a future setup date on accounts.
296 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
299 edit (not just import, export and allow default/fixed) arbitrary radius stuff
301 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
303 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
305 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
307 what else (besides l10n) for i18n? (money!)
309 audit htdocs/* for things that should be libraried and things that should be
310 new methods on the objects (need to do this before implementing a new UI)
311 all the big things are done
313 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
314 Decide based on whether or not the "error" should show up in logs.
316 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
317 for HTML creation. Maybe Embperl or something along those lines. ?
319 When running bin/bill, Fix this (Annoying but harmless):
320 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
321 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
322 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
324 all cgi (but internal to the isp) places where package names are listed should also have
325 comment (like agent_type)
327 clean up $recref and other silliness and use -> calls where possible, or
328 one other alternative. clean up everything else.
329 should FS::Record use Tie::Hash? That would be very clean, but where do we
330 store the other information? Maybe you could ask any FS::Record object for a
333 change all file access from regular open(FILE,) stuff to OO, because of
334 problems scoping and passing filehandles like that.
336 the web interface should create a new object and use it instead of a blank
337 form for new records. the create method of svc_ objects should set defaults
340 sub check in man FS::table_name should be rewriteen. Get rid of $recref
341 stuff. Make sure all fields that refer to other database are checked.
343 Integration with signup disks (are there any free ones? Netscape?).
345 One-button cancel (+refund) for lusers who can't get online.
347 Keep information on virtual web servers (hostname, IP, host machine,
348 directory, etc.) and export this information for importation into the ISPs
351 Remove requirement that the first mail alias be the catchall? Still make
352 sure only one catchall per domain is defined in any case, of course.
354 Ability to move cust_pkg records from one customer to another? (proably
355 will need to cancel the old and create a new like when we move services
358 Auto-increment expired cards one year, and try again?
360 More non-US stuff - zip codes, country codes, foreign currencies, etc.
362 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
364 Nicer set of integrated reporting possibilities, like weekly sales totals
365 by customer, package, agent, referral, etc., aging reports sorted by lots
366 of different things, and so on.
368 Client/server setup for users to modify their own passwords, shells, etc,
369 via passwd or secure web interface (prelminary passwd/chfn/chsh
370 replacement done). Complicated by the fact that we don't want to allow
371 incoming connections to the machine running Freeside, so we probably need
372 to have a daemon on each external shell or web machine that is contacted
373 by the Freeside machine. Be very very careful for both traditional
374 security issues and DoS problems.
376 An extension of the above to allow users to modify selected parts of their
377 own information, order and cancel services. A web interface for new
380 Expand domain name stuff to house all domain information. Export
381 named.boot/named.conf (primary and secondary) and named.{domain} files.
382 Add more registries (not just InterNIC's com org net edu)
384 Nice postscript paper invoices, rather than current ASCII invoices.
386 think about race-condititions in FS::Record and derived ->check ->insert
387 and so on, uid and username checks in svc_acct, etc.
389 Move to rsync over ssh file exportation rather than scp.
391 check 'n fix the proactive password checker. (cracklib?)
393 refunds of "BILL" payments: generate pseudo-check.
395 write batch senders and batch parsers for the different credit card processors
397 More CC processors/methods.
399 you should be able to fiddle the setup date in cust_pkg. (at least initially)
401 delete options in administration section
403 write a generic batch senders and batch parsers.
405 need a way to override svc_acct export on a per-machine basis; just use config files based on machine name i suppose; document that. (no, import desync_hosts
406 type stuff from cerkit)
408 add a table with column of export services (passwd, shadow, master.passwd, .qmail file update, dns update, etc.) and rows machine groups and whether or not to export that (and any necessary parameters). wasn't matt (vunderkid, not matt@michweb) working on this? find him? each machine goes in a group of its own as well as a group based on function. add a table with only svcpart and machine group. now, when you import from each machine, it can get its own accounts with one svcpart and universal accounts with another svcpart. (though that does make the username duplicate checking more interesting)
410 you should be able to get column types as a method against an FS::Record object
411 as well as dbdef->table($table)->column($column)->type
413 move to perl module for fuzzy and soundex searching.
415 package view needs to list extraneous services; we need to prevent the
416 creation of them so this never happens (and mark it as such in the source)
417 (the creation problem should be fixed - though they will still happen if people
418 fsck around in the data manually, so list them anyway)
420 add attribute dictionary to fs-setup as a menu, plus analyze users file to
423 Check for and report on duplicate billing accounts (cust_main, though many
424 will have a need for these so probably don't disable them outright.)
426 create a ->warn as well as a ->check method for all FS::table classes?
429 something to automate making a release and updating the web demo
431 export a debian-style (also redhat and?) /etc/group file aswell!
433 svc_acct_sm.import qmail import should pull in recipientmap people too.
435 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
436 should fork and do them in a child.
438 i18n/l10n: take ALL messages and catalog them in english.txt or in database or something, so we can eventually go int'l. int'l currency support would be a help aswell.
440 get some of { city, county, state, zip } from the missing bits if
441 possible (where can i get the data to do this? usps.gov?)
443 additional interfaces (perltk? java?)
445 Put the GPL notice in all files.
447 integrate w/IDEA's signup server
449 $cust_bill->owed database field to be eliminated, replaced by a method call
450 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
451 same for cust_credit->credited
453 Export quota information.
455 move all configuration to a central place. maybe in blob's in the
456 database. maybe even things like the code to execute when a username is
457 changed can be in there, so less of the distributed scripts change between
460 Implement setup and recurring fees as Safe perl expressions rather than
461 numbers, to allow for variable-rate services. Backwards compatibility is
462 obtained because { 43 } in perl is still 43. :) Define API to pass
463 starting and ending dates and any other necessary data to expression
464 (fees are currently evaluated as Safe expressions but more work needs to
465 be done to define an opmask for various needs, write examples
466 (usage-based billing, etc.) and so on).
468 Add the ability to modify the next billing date in cust_pkg, and take
469 appropriate action. This will allow the implementation of pro-rate/1st of
470 the month billing as well as the ability to manually fiddle with
471 anniversary dates in cust_pkg, so you can sync a customer's anniversary
472 date even if you're using anniversary billing (manually or automatically).
473 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
474 charges - anything more complicated should figure it out itself given
475 starting and ending dates [document that!])
477 Daily Radius log parsing into database; other logfile formats?
479 Callbacks to enforce hourly limits on accounts (suspend until the end of
480 the billing period?), for those who limit customers rather than tack on
483 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
484 example) need to charge tax on equipment but not service (separate flags
485 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
486 recur_tax and recur_notax fees, and possibly something more flexible if
489 Allow for a variable number of invoices for customers who need multiple
492 Add a mail alias service with table svc_acct (not domain mail aliasing
493 which is domain with svc_acct_sm)
495 (bring back from fsold) Change customer comment field from its current kludge to something more
498 Better work orders with more information. Should eventually open a ticket
499 when we have such a thing.
501 edit/process/svc_wo.cgi
502 Call tracking and trouble tickets.
504 More accoutability for complimentary accounts: approval, expiration, term
505 (no more than x months in advance) and notification.
506 Flag particular users (or all users, for that matter) as having their
507 passwords hidden and/or locked from users of Freeside (maybe need Freeside
508 security levels first?).
510 Better Freeside-level configurable access, for those ISP's who have
511 employees they can't trust. Right now you're "stuck" with setting up
512 .htaccess stuff yourself. This should really just be integrated.
514 configuration/setup should get web interface
516 /usr/local/etc/freeside should be configurable
518 (probably as part of some automated installation process?)
520 This requires some serious magic in FS::Record:
521 ok, if date_type in fs-setup is to be something besides int,
522 now we need to create wrappers
523 for them so they behave identically across RDBMS's, ie date pops out as as
524 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
525 is a string not a hashref for backwards compatibility?) and so on. (remember
526 to treat '0' as Not a Date instead of 1/1/70.
528 Add Freeside-level transactions for RDBMS's which don't support
529 transcations? (Currently we assume a minimal RDBMS which has no rollback,
530 transactions or atomic updates). Or just require a RDBMS that supports
531 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
532 interface had this kludge on top of it but is a technical dead-end in most
533 other ways, unless it can gain an SQL parser and DBD interface.
535 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
536 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
537 an FS::Record have something to do with a tied hash? But we don't want
538 performance to go gaga... maybe something with commit to help out here?
540 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
542 Better automated comparison of our CC records with processors (CyberCash,
543 at least, has not always had 100% accuracy, though recent versions are
546 Expect or other pty based login check, where we actually connect to a
547 terminal server or shell machine and test logging in as the user (if we
548 are keeping a cleartext password for that user) (This is something tech
549 support often needs for new customers)
551 Use cust_main table for pre-sales tracking as well?
553 Automatic commision report and check generation via freq and prog (to
554 become a Safe perl expression) fields in agent table, and possibly others.
556 Database and add a mailed-out date and method for disk/CD mailing, so a
557 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
560 Inventory tracking for physical items such as routers (for sale or
561 lease... probably doesn't make a difference in the ordering... but if you
562 cancel a router lease the inventory should come back. hmm.)
564 -- Matt's wishlist ---
566 From matt@michweb.net Fri Feb 20 16:39:53 1998
567 Date: Thu, 19 Feb 1998 23:20:11 -0500
568 From: Matt Simerson <matt@michweb.net>
569 Reply-To: quadran-developer@netgoth.com
570 To: quadran-developer@netgoth.com
571 Subject: Re: Welcome to quadran-developer
573 >Whats it based on and what is it supposed to do? I'm interested, but
574 >unfortunatly, I don't have that much time to help on the project (I'm busily
575 >working on one of my own based around MySQL and Qt right now -- don't know
576 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
577 >it is designed around our system)...
579 That's what I set out to find, but didn't find anything on the web site.
580 I'm looking for something that will do the following:
582 Single point of entry for users on a secure system:
583 Creates account on user (public) systems
584 update /etc/passwd/master.passwd file
585 update radius database (if necessary)
586 Set up up disk quotas (although I hacked adduser to do this)
587 Option for adding user to a mailing list(s)
588 Export of new user info to customizable report (for automated entry
590 accounting software, etc...)
593 Export credit card info for batch processing and have hooks built
594 in for other forms of electronic processing.
595 Batch-Payment (apply payments from formatted text file).
596 Customizable reports for manual entry/importing into Accounting
598 Email or laser print invoices
599 Sanity checks credit card numbers before processing (code available)
601 Simple method for disabling an account.
602 Arbitrary Expiration Dates (on a given day, in x days)
604 Changing password to '*'
605 Virtual customers disabling dns, http server, log processing, etc..
607 Billing for different account types:
608 Dialup monthly flat rate. Prorates for partial months.
609 Dialup monthly flat rate for x hours + hourly usage.
612 Virtual Web accounts - w/multiple mailboxes
614 Disk space used over quota.
615 Tech support minimum + hourly charges
616 Other for misc stuff (modem, RAM, etc...)
618 Per user definable RADIUS attributes (ties in with above)
621 IP filters (for dialup email only)
623 Keep logs of modem usage generated daily from radius accounting logs stored
624 on multiple radius servers.
626 Keep logs of disk usage generated from quota.
628 Method of adding virtual domains to your system:
629 Automatically grabs an IP address from a preassigned pool.
630 Creates a domain.com database file from database fields
631 Updates /etc/named.conf or /etc/named.boot and reloads named.
632 Add's virtual.com to /etc/sendmail.cw or qmail control files.
633 Edits your web servers httpd.conf file and restarts http server.
634 An optional section for adding vif's can be added if the users OS
635 supports adding them on the fly. Otherwise it's up to the end
636 user. Make a hook that can run a custom script that the user
637 tweaks for his system.
638 Update or create the config file your web stats analyzer needs. I've
639 done this for analog (free) and http-analyze. Probably
640 should only officially support analog and let users hack
641 it to their hearts desire.
642 I've already written scripts that do most of the virtual web stuff on my
643 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
644 as long as all the info was stored in the database (username, domain name,
645 and ip pool) this could easily just be run as an external script that the
646 user tweaks to match his system.
648 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
649 Payroll, Tax stuff, and most everything else we could need. It's already
650 set up for the type of checks we have, etc, etc... I just need something to
651 do the billing part. I can import/export sales and payments directly once
652 the billing part is done. You can't write accounting software as good as