Ticket #90 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

debathena-discuss-server doesn't create inetd/xinetd service

Reported by: tabbott Owned by:
Priority: low Milestone:
Component: Keywords:
Cc: Fixed in version:
Upstream bug:

Description

The debathena-discuss-server package apparently doesn't work. It's never been tested, so this isn't surprising, but this should probably be fixed if Discuss is to survive the move to Athena 10.

Change History

comment:1 Changed 13 years ago by mitchb

  • Summary changed from debathena-discuss-server doesn't work to debathena-discuss-server doesn't create inetd/xinetd service

The package just needs to create the inetd or xinetd service (I guess after determining which one is appropriate). It's basically fine other than that.

There's also some initial configuration that might be done, like setting up the ACL for who can create new meetings, but I don't think there's a good way to do that without interrupting the user for interaction, and root@localhost can create meetings without being on the ACL, I believe.

Of course, a discuss server also requires a keytab and/or srvtab. Clearly the package isn't going to fetch those. Is there any sort of reminder mechanism we use for other such packages to tell the user they need to go about doing this? (In the mkserv world, services get to add messages to be displayed to the user at the end of the mkserv run, such as reminders to change the root password, to get srvtabs, etc.)

comment:2 Changed 13 years ago by broder

  • Status changed from new to closed
  • Resolution set to fixed

r23530 adds the inetd service, along with some small fixes in r23531, r23532, and r23533.

The best mechanism for telling the user how to do initial configuration is the README.Debian file, which is installed into /usr/share/doc/$PACKAGE/

I don't really have enough knowledge about discuss to write such a file, but if you'd like to write one, I'd be glad to drop it in.

Note: See TracTickets for help on using tickets.