irc server admin basics
Dan Rawson
development team, and I'm starting completely from scratch . . .
I've found plenty of FAQ's etc. (even books) on the client side, but very little other than the documentation in
ircd.conf on the server <g>
As an aside, I can't get to any of the public IRC servers from inside our corp. network. If there are IRC channels
which provide these resources out there, I would have to get to them from home.
TIA . . . .
Dan
Contention
>Is there a good source for server admin basics?? I'm setting up an IRC
>server on our intranet for use by our development team, and I'm
>starting completely from scratch . . .
http://www.irchelp.org/irchelp/ircd/
http://www.ircdhelp.org/
There's an artificial but nonetheless real difference between
setting up an IRC server and being an IRC admin. The joke is that anyone
can set up an ircd. Sometimes people do run into stupid problems, but
it's a simple task for most *nix users and most ircds. What isn't so
simple is the day to day job of running a public IRC server and
remaining both motivated and sane.
If you're setting up an internal server, you probably *don't* need
anything more than a basic knowledge of UNIX/IRC and a guide to the
ircd.conf file. Configure server, build server, write ircd.conf file,
run server. Everything else, from network routing to services to dealing
with users, is irrelevant to your situation.
HTH,
Contention.
--
Andrew J. Shore, Contention-among-dragons.
"Win. If you can't win, change the rules. If you can't change the rules,
cheat. If you can't cheat, don't play. If all else fails and you have to
play - play to lose."
Delta5
deal with routing, netsplits etc.. The coding groups write a few help files
but not in basic terminology. I havnt found much written help on this stuff.
If anyone would like to take part in the writing of an admin manual, I would
be glad to serve it on my up and coming irc website i am planning.
Delta5
Founder
USAchat Network
irc.usachat.net
www.usachat.net
www.irc-forum.stormhosts.com
SpEaRmAn
If you dont know... Then your probably dont need to.
Only reason I could see someone setting up an IRC server is for business
use.. There are plenty of IRC networks out there already and no more need to
be made.. It would of better with just one..
"Delta5" <admin@(remove)usachat.net> wrote in message
news:6kQ8a.237$I_1....@cletus.bright.net...
Contention
>Only reason I could see someone setting up an IRC server is for business
>use.. There are plenty of IRC networks out there already and no more need to
>be made..
Servers, and admin, come and go all the time. Passing on some of the
experience admin have gained the hard way would be a Really Good Thing.
There are problems with the idea, though. The technical information, you
can get by reading RFC 1459 and keeping your eyes open for a while; a
lot of the rest is intuition and technique which would take a real
effort to put down in coherent form, not to mention that it's horribly
network specific.
A complete IRC admin's guide would have to include a guide to user
psychology, a treatise on how to enforce rules fairly, a book on how to
enforce rules anyway, a collection of notes on IRC politics, a manual on
TCP/IP, a pamphlet on IRC and network viruses, and RFC 1459 with notes
on updates. Not to mention leaflets on the various services and IRC
history, and...
What we *have* is a collection of common wisdom passed around the
virtual campfire from one IRCop to another, aphorisms such as "Never
give an O: line to someone who asks for one."
>It would of better with just one..
The differences between networks and the choice users have is one of
IRC's strongest selling points.
SpEaRmAn
make their own services.. they all suck.. point proven.. if it was just
Efnet and Dalnet the world would be much better.. because then people would
be able to talk to more people rather than going to dalnet for windowshelp
freenode for for open source help etc.
"Contention" <Conte...@soaring.demon.co.uk> wrote in message
news:IYNXnSL0x$Y+E...@soaring.demon.co.uk...
Contention
>tell me the differences between ChatNet and any new start up.. most try to
>make their own services.. they all suck.. point proven..
I don't think many people will find your argument terribly
convincing. I know I don't. :) I am currently chatting on two medium
sized networks with completely different purposes and rules to match.
Delta5
network "z" is run, I can create my own. At least with open source software,
it wont cost me a fortune. Try that with voice chat. You sound like someone
that lost his o-line over something stupid I imagine. Why would you care if
someone started up their own network anyhow. Nobody is twisting your arm to
go there. And as far as services go, Dalnet is not the last word in services
or daemons either. I used to have a channel on dal for awhile and I happen
to think their services are a bit weird.
But thats my opinion, and I have chosen to use Epona.
Your idea that "if I dont know, I probably dont need too" and that there
should be only one irc network is about a laugh. People are free to do what
they want and thats what the internet is all about. I am happy to see a
group attempt to start a new network. Im not talking about the kiddie dsl
networks either. I am talking about someone that starts a real server and
gets a good domain name.
SpEaRmAn
fagots.. but just stay away from em
"Delta5" <admin@(remove)usachat.net> wrote in message
news:tlU8a.31$lf3....@cletus.bright.net...
Andy Smith
> tell me the differences between ChatNet and any new start up.. most try to
> make their own services.. they all suck.. point proven.. if it was just
> Efnet and Dalnet the world would be much better.. because then people
> would be able to talk to more people rather than going to dalnet for
> windowshelp freenode for for open source help etc.
I disagree, there is plenty of scope for middle grounds between dalnet and
efnet. dalnet _cannot_ provide the more whizzy aspects of services simply
because they have so many users.
While it is of course true that many IRC networks are started as purely ego,
desire to have "power" over some group of people, and have nothing new to
contribute to the IRC world, even that can be useful as a way for the staff
to grow up. :)
--
The Blitzed IRC Network
http://blitzed.org
Andy Smith
> actually i never have had an oline and dont want one.. all ircops i know
> are fagots..
You have been chatting on irc.homo.de again?
SpEaRmAn
"Andy Smith" <grif...@blitzed.org> wrote in message
news:Vx49a.14238$Jj4.11...@news-text.cableinet.net...
Dan Rawson
> Dan Rawson <daniel.rawson.take!this!out!@asml.nl> wrote:
>
>> Is there a good source for server admin basics?? I'm setting up an
>> IRC server on our intranet for use by our development team, and I'm
>> starting completely from scratch . . .
>
>
> http://www.irchelp.org/irchelp/ircd/
> http://www.ircdhelp.org/
>
> There's an artificial but nonetheless real difference between
> setting up an IRC server and being an IRC admin. The joke is that anyone
> can set up an ircd. Sometimes people do run into stupid problems, but
> it's a simple task for most *nix users and most ircds. What isn't so
> simple is the day to day job of running a public IRC server and
> remaining both motivated and sane.
> If you're setting up an internal server, you probably *don't* need
> anything more than a basic knowledge of UNIX/IRC and a guide to the
> ircd.conf file. Configure server, build server, write ircd.conf file,
> run server. Everything else, from network routing to services to dealing
> with users, is irrelevant to your situation.
>
> HTH,
>
>
> Contention.
Dan