Dear,
Sorry I did not realize that I did not have inetd installed, so my fb classic
was just not started.
And by "support classis", I mean something that can connect directly to
database file, not through network.
Now the classic server started, the problem is solved.

Thanks.

On 2007年12月24日Monday 17:36:29 Lele Gaifax wrote:
> On Mon, 24 Dec 2007 16:53:28 +0800
>
> Magicloud Wang <magicloud.magiclouds@...> wrote:
> > Dear,
> > The main difference I got is that classic does not have a tcp
> > port listened, right? I just tried classic the first time this
> > morning, isql can connect to the database, while netstat reported no
> > port related to firebird.
>
> No, there's really no difference, from the user/client point of view,
> between classic and superserver. There is instead a big difference in
> how the *server* works: in the first case (classic), there's a single
> process per connection, [on Unixes] launched by inetd [or xinetd]: you
> won't find any firebird process running, when there are no connection
> to any DB on that machine. In the superserver case instead there's a
> single multithreaded FB process always running waiting/serving any
> request to the DB.
>
> To be of further help, some more details are needed, such as hosting
> operating system and Firebird version.
>
> hth,
> ciao, lele.