29 Jan 16 08:42, you wrote to me:

 WV>>> But when you are running binkd as a daemon I don't think you want to
 WV>>> use a users private appdata directory for this, but maybe you
 WV>>> should?

 ml>> wait, what? are you ""stuck"" on one machine, one person? i certainly
 ml>> do not want other folks' mail in my stuff nor do i want mine in
 ml>> their's... they can run their own point or node with or without full
 ml>> bbs if they want and i'll run mine... long gone are the days where
 ml>> one machine is tasked with one job... now those types of things are
 ml>> done per account and machines have numerous accounts... each standing
 ml>> alone and separate from the others...

 WV> You do have a valid point, although I think your usecase is very unlikely.

maybe, maybe not...

 WV> But what does happen is that sysops with more than 1 nodenumber
 WV> (sometimes in fidonet, sometimes in different othernets), want to run
 WV> more than 1 instance of binkd with seperate configurations. If they
 WV> run those in different user accounts, you don't want to have those
 WV> binkd instances look in the same location for their default
 WV> configuration file.

right...

 WV> So although binkd is a server application and can be run as a daemon,
 WV> APPDATA might be a good place for the default binkd configuration file
 WV> location...

thank you ;)

)\/(ark

... By all means, let's not confuse ourselves by the facts.
---