nchat-users

[Nchat-users] building probmes in nchat-3.3

[chino <zy...@te...>]

Hi again, I have been useing nchat v3.25 and v3.3beta9 without any
problem but when I started to build the v3.3 binaries I get this error:

nchat@GORGOROTH:~/nchat-3.3$ make

-- Building NexusChat Server
gcc -Wall -O2 -c nchat.c
nchat.c: In function `save_config':
nchat.c:570: error: structure has no member named `quiet'
make: *** [nchat.o] Error 1

Any Idea?

Thanks in advance

Re: [Nchat-users] basic questions

[Bryan B. <bb...@ea...>]

On Wednesday 19 January 2005 7:07 am, chino wrote:
> I need to run nchat like root because chroot enviroment requiered it. So
> who is realy running nchat, root or nchat user?

Since you have the user option set, after NexusChat does the chroot() it will 
drop its root privs and become the nchat user.  So it is actually running as 
the nchat user.

> Ok another question: I set somewhere the max number of user [999], but
> when I type /s I can see " 14 ports opne ", one port by user, so when
> there are 15 users chatting there are 0 ports open and noone can login
> in the chat. What is the meaning of those ports? How coud I increase it?

That max number you are talking about was referring to the database size.  You 
want to change the number of max ports.  There is an option to change it in 
the setup.sh program, or you can edit config.h and change the MAX_USERS 
variable to whatever you want.

I also wouldn't suggest setting MAX_USERS to 999 for speed reasons.  I would 
set it to the most users you have ever had online at the same time and maybe 
add 10 to that.

Hope that helps.

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] basic questions

[chino <zy...@te...>]

Hi all, I have some basic questions about the nchat daemon.

Im running nchat 3.25pre3 under Linux, and I have a system user called
nchat to run it. Ok there is my nchatrc

 NexusChat Resource File
# make sure you put "" marks around text values with spaces
#
port = 5000
locked = false
staple_time = 60
guest_kill = true
#quiet = true
#check_dup = true
ping_hack = 0
chat_name = "|f15LAST|f12WORLD"
user = nchat
#group = nogroup
chroot = true
#broadcast_priority = 10
#ask_ansi = true

I need to run nchat like root because chroot enviroment requiered it. So
who is realy running nchat, root or nchat user?

Ok another question: I set somewhere the max number of user [999], but
when I type /s I can see " 14 ports opne ", one port by user, so when
there are 15 users chatting there are 0 ports open and noone can login
in the chat. What is the meaning of those ports? How coud I increase it?

That is all
-Thanks for your time-

[Nchat-users] NexusChat 3.3-BETA9 Released!

[Bryan B. <bb...@ea...>]

CHANGES FOR 3.3-BETA9 RELEASE
------------------------------------------------------------------------------
- Bug fixes
- Code and visual cleanups
- Added a new profile system where users basically get to maintain their
  own /m box.  /profile allows users to edit their profile which can be
  viewed via /m(user#) or at the end of the /last(user#)
- Added a handle_notify config option that broadcasts when a user changes
  their handle, and shows their new handle.
- Added a /sc command to only show users in the same channel as the
  user
- Added ip_priority setting so you can change what classes can see IP
  Addresses in /s#

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] NexusChat 3.3-BETA8 Released.

[Bryan B. <bb...@ea...>]

The major focus of this release is bug fixes.  There is nothing very serious 
here, but some of these bugs can cause NexusChat to not function as intended.  
Users of beta versions are advised to upgrade.

CHANGES FOR 3.3-BETA8 RELEASE
------------------------------------------------------------------------------

- Many bug fixes (release focus)

- A new channel can now have a specified limit when being created.
  For example, typing '/c test 10' will create a channel test (if it does not    
  exist) and set the limit to 10.
  [FEATURE REQUEST]

- Added a list and next command to user editor

- Separated console shutdown from remote, and logs who did it

- Added /zhalt command to shutdown nchat

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] Bug Fixes, New BETA release

[Bryan B. <bb...@ea...>]

NEW BETA7 RELEASE

There were a couple minor, but annoying bugs in the last BETA release, they 
have been fixed.  Read the changelog below for details.

CHANGES FOR 3.3-BETA7 RELEASE
------------------------------------------------------------------------------

- There was a newly introduced bug in which a user was not saved when
  they logged out.  Also the flags, such as color and echo where not
  loaded from the database when a user logged in.

- Added functionality to save connected users on a shutdown.

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] 3.3-BETA6 Released!

[Bryan B. <bb...@ea...>]

The next development release is now available.  The complete changelog is 
below.

CHANGES FOR 3.3-BETA6 RELEASE
------------------------------------------------------------------------------

- Many minor visual changes, just cleaning up the display of some commands
  and output screens.
  
- Originally it was hardcoded that guests couldn't use color codes in their
  handles, but they could in chat and other places.  Honestly I don't 
  remember why I took out colored guest handles, but the idea of letting them
  use it elsewhere and not in handles was stupid.  So now there is a new
  option called color_priority, which allows you to block whatever classes 
  you want from using color codes, and it applies everywhere in the chat, not
  just in the handle anymore.  By default color_priority = 0, meaning anyone
  can now use them.
  
- The way the registration system worked was: A user enters their info, a
  disabled account is created, and they are disconnected and told to wait
  until a sysop validates them.  Some people complained about that system, so
  now you can have it how you want it (maybe)
  
  If you create a NEW class in the nc_class file, then instead of logging
  them out and telling them they have to wait, their account will be created
  and activated, and they will be sent back to the login where they can use
  their new account.  They will still be of the NEW class, but you can give
  the class whatever access you want.  NexusChat will ship with a default
  NEW class that will just inheret from GUEST.  So basically they get to
  use their account number and save their preferences, but they are still
  subject to guest access (ie. can be vote killed, no email, etc)
  
  This is the way I suggest doing it, instead of giving them user rights
  immediately, but now its up to you.  Also, if you make NEW inheret from 
  USER, you still need to change their class to USER at some point, unless
  you want all your user classes to be NEW.
  
  NOTE: You can also change the macro NEW_CLASS in class.h to set a new
  user's class to whatever you want.  So if you want them to automatically
  become full fledged users, just change NEW_CLASS to "USER"
  
- Now, in the user editor, when you set a user's class, it will automatically
  set their node flags, and their time limit, even if they were already set.
  This should make it less of a hassle to change a class.

- Added a User Since field to the database which is set when the account is
  created, and cannot be edited.  It is displayed in the user editor, /last,
  and /us.

- Added extended help for /mail, /us, /ud, and /q

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] New Releases (Bug Fixes! ..and more)

[Bryan B. <bb...@ea...>]

RELEASE 3.25pre3 (12/22/04)
--
A possible DOS bug had been fixed in versions prior to 3.25pre3.  It may be 
possible for a user to hang all connections if the ask_ansi option is 
enabled.  If you use this option, you should upgrade as soon as possible.


RELEASE 3.3-BETA5 (12/22/04)
--
The 3.25 bug has also been fixed in this version, but another bug in the 
saving of user records has also been fixed.  Users of the BETA version are 
strongly urged to update to BETA5.

Some new additions and changes are also in this new BETA release.  Check out 
the changelog for this version at:
http://sourceforge.net/project/shownotes.php?group_id=1613&release_id=291717

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

Re: [Nchat-users] [nchat] add users

[Bryan B. <bb...@ea...>]

On Fri December 17 2004 04:25 am, chino wrote:
> Hi all, I cant find in the docs how can I register or add sysops and
> users. Someone could help me?
> Thanks.

There are two ways to create and edit users.  You can use the user editor in 
nchat, just type '/ue' to enter the user editor.  To create a new user in the 
editor type 'load <user>' where <user> is the user number you would like to 
create.  You will then be presented with a blank user which you can edit.  If 
you set their Class first, it will fill in default data for you.  To create a 
sysop, enter 'sysop' as the user's class.  Typing 'quit' will then save the 
user and exit the editor.  You can type 'help' in the editor for a list of 
commands.

The second way to edit the user is via the command-line utility called userdb.  
Run 'userdb' by itself for a list of options.

-- 
Bryan Burns a.k.a "Haplo" <bburns3earthlink.net>

[Nchat-users] [nchat] add users

[chino <zy...@te...>]

Hi all, I cant find in the docs how can I register or add sysops and
users. Someone could help me?
Thanks.

[Nchat-users] from IP limit?

[[gill] <gi...@to...>]

Hello,

I'm running NC on a system and some of my users connect from behind a
firewall.  Thier internal network addresses are translated to a single
public IP address so when more than one of them are on /s shows one IP for
all of them.  When one user is on I have had up to two guests on from that
IP but another user-class ID cannot log in.  After creating an account for
the new user I will /rl# and send 'em back to login and they put in the ID
and put in the passwd and then hang until the login times out.

Is this expected, or have I got something misconfigured somewhere?

thanks!

--gill

[Nchat-users] Test

[Bryan B. <ha...@ww...>]

Just testing.