Bug 508290 – app-admin/conserver - src_configure() should not set --with-port

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description charmont.chen 2014-04-21 02:43:00 UTC]

The default port for conserver is 782, while gentoo compile it `--with-port=7782`

When I'm connecting to other console server, I have to specify the port with `-p 782`, otherwise it will fail with 'console: connect(): 7782@****: No route to host'. This is undesired.


Reproducible: Always

Steps to Reproduce:
1. console -V

Actual Results:  
console: conserver.com version 8.1.18
console: default initial master server `localhost'
console: default port referenced as `7782'
console: default escape sequence `^Ec'
console: default site-wide configuration in `/etc/console.cf'
console: default per-user configuration in `$HOME/.consolerc'
console: options: libwrap, openssl, gssapi, pam
console: openssl version: OpenSSL 1.0.1g 7 Apr 2014
console: built with `./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-openssl --with-pam --with-libwrap --without-dmalloc --with-gssapi --with-logfile=/var/log/conserver.log --with-pidfile=/var/run/conserver.pid --with-cffile=conserver/conserver.cf --with-pwdfile=conserver/conserver.passwd --with-master=localhost --with-port=7782'


Expected Results:  
no '--with-port=7782'

http://www.conserver.com/docs/conserver.man.html

−p port
		
Set the TCP port for the master process to listen on. This may be either a port number or a service name. The default port, ‘‘conserver’’ (typically 782), may be changed at compile time using the --with-port option. If the --with-uds option was used, this option is ignored.

[Comment 1 Yixun Lan 2014-09-09 06:50:29 UTC]

don't know the history, but may I ask why should we change the port?
is there any conflicts?

as I can tell, this change will just result in this error..

[Comment 2 Sergey Popov 2014-11-18 08:30:07 UTC]

(In reply to Yixun Lan from comment #1)
> don't know the history, but may I ask why should we change the port?
> is there any conflicts?
> 
> as I can tell, this change will just result in this error..

/etc/services does not describe neither 782 nor 7782 port, --with-port was added back in 2003. I can not see why we should not stick to the program defaults in this case, so i am for dropping --with-port from ebuild and leave apropriate note in pkg_postinst about this

[Comment 3 Jonas Stein 2017-07-22 18:56:22 UTC]

dan, can you discuss this with the other developers and find a solution together, so that we can close this eventually?

[Comment 4 Daniel M. Weeks 2018-05-07 20:32:13 UTC]

From the original ebuild (7.2.3) on the original bug # 8652:

> 	# Conserver normally uses port 782 for its client/server, but
>	# this should restrict itself to the local machine only, on a
>	# non-privledged port (7782).

In my opinion we should keep the current behavior port using 7782:

1. Upstream shouldn't be using 782. It isn't assigned.
2. Conserver shouldn't need to run with higher privileges just to use a system port.
3. The package has been configured this way since its inception in Gentoo 14.5 years ago. (This configuration was a conscious choice, not a mistake.) I'm not arguing against changing it to maintain the status quo. I don't think changing (breaking) the default for all Gentoo users to make it more familiar/easier for non-Gentoo use cases is justifiable.
4. An alias is an easy workaround for non-Gentoo use cases.