Ticket #723 (new defect)

Opened 4 years ago

Last modified 4 years ago

debathena-discuss-server should symlink /usr/spool to /var/spool

Reported by: jdreed Owned by:
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

/usr/spool/discuss/foo is the hardcoded path to discuss meeting in most places, including (apparently) diswww.

This means that users attempting to use diswww to access a meeting on a Debathena discuss server will get told that the meeting does not exist.

We should (presumably in the postinst) symlink /usr/spool to /var/spool.

Change History

comment:1 Changed 4 years ago by jdreed

FHS says that /usr/spool -> /var/spool symlinks are acceptable for legacy apps.

There's an argument to be made that discuss-server should symlink /usr/spool/discuss instead so it doesn't magically end up functioning as debathena-solaris-compat or something.

Anders notes it might be preferable to just patch the discuss server to just DTRT.

There's also an argument to be made that this is diswww's fault, since at least the 9.4 source shows /var/spool as the canonical path.

comment:2 Changed 4 years ago by jweiss

I could have sworn that ghudson added a patch to discussd years and years ago that caused it to read /usr/spool/discuss as /var/spool/discuss. Did that patch get lost, or did I mis-remember exactly what the patch did.

Note: See TracTickets for help on using tickets.