Bug 18931 – patches to make xfs init and conf scripts more rational

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description James Bowlin 2003-04-07 17:33:11 UTC]

The comments in /etc/conf.d/xfs are incorrect and confusing.  In order to fix it properly 
I need to change /etc/init.d/xfs so that the XFS_PORT variable could be commented 
out in the config file. 
 
 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



This is a very minor fix.  It will help people who read the xfs config file. 
Incorrect comments are worse than no comments.  As a side benefit 
the xfs init file is streamlined and easier to understand. 
 
I will post the two patch files as attachments.

[Comment 1 James Bowlin 2003-04-07 17:35:59 UTC]

Created attachment 10344 [details, diff]
Patch for /etc/init.d/xfs

[Comment 2 James Bowlin 2003-04-07 17:36:40 UTC]

Created attachment 10345 [details, diff]
patch for /etc/conf.d/xfs

[Comment 3 Tiago Freire 2003-04-08 12:42:36 UTC]

it is listed as minor, but this incorrect comment causes trouble, nd this might fix some 
OpenOffice startup issues (!!!). 
OpenOffice was completely broken fter compilation on my machine, nd I use XFreee4.3 
masked at the time of this writing (so, some part of my system is using '~x86'). 
Then I unmerged and installed openoffice-bin, and it STILL didn't work. 
after a long search in the forums, I found some workarounds, saying that i had to change this 
flag, and the comment was wrong. I came to bugs.gentoo to search if this bug was already 
filed, and this one here is not the same bug, but touches the same crucial part of the problem 
with openoffice-bin on machines which freetype is newer than the freetype which openoffice-bin 
was compiled with.  
part of the OpenOffice problem is related to XFree not using xfs, because of this problem with 
xfs configuration.  My xfree wouldnt find xfs on unix:127.0.0.1:7100 because of this config 
problem. 
 

[Comment 4 Martin Schlemmer (RETIRED) 2003-04-08 15:35:29 UTC]

1)  The comment says clearly that a value of '-1' means it will only listen
    on unix sockets, and NOT tcp.  MEANING that if you want it to listen on
    tcp, you need to set XFS_PORT to whatever port you want it to listen on
    and comment the "nolisten = tcp" line in /etc/X11/fs/config.

2)  I never heard of 'unix:127.0.0.1:7100'.  You CANNOT have a unix socket
    with an IP and PORT ...

This sounds like confusion/lack of knowledge on the users part, so marking
invalid.