On Nov 1, 2015 6:09 PM, "Ron W" wrote:
>
> On Sun, Nov 1, 2015 at 4:14 AM, Stephan Beal
wrote:
>>
>> But if it only stores a pointer, and requires the user to reconstruct
the link, it's not terribly useful/friendly. The user would potentially
have to replace fossil's placeholder pseudosymlink fil
On Sun, Nov 1, 2015 at 4:14 AM, Stephan Beal wrote:
> But if it only stores a pointer, and requires the user to reconstruct the
> link, it's not terribly useful/friendly. The user would potentially have to
> replace fossil's placeholder pseudosymlink file with a link of his own
> (which he could
On Sun, Nov 1, 2015 at 2:14 AM, Stephan Beal wrote:
> On Sat, Oct 31, 2015 at 10:19 PM, Matt Welland
> wrote:
>
>> On Sat, Oct 31, 2015 at 1:47 PM, Stephan Beal
>> wrote:
>>
>>> On Sat, Oct 31, 2015 at 9:41 PM, Matt Welland
>>> wrote:
>>>
BTW, to some extent it is ok for fossil to be opin
Hello All,
Not sure if this means anything but I peaked at config.log after
building fossil from source:
FreeBSD 10.2-release:
% cat config.log
Invoked as: ./configure --with-openssl=/usr/local/bin/openssl
Failed: cc -g -O2 conftest__.c -o conftest__
/tmp/conftest__-f2b4ed.o: In function `main':
Hi all,
Thanks to all of you who have responded. I have managed to find the program
that was hogging the port and therefore got Fossil up and running again.
Thanks.
Damien.
-Original Message-
From: Thomas Schnurrenberger
Sent: Sunday, November 01, 2015 12:44 PM
To: fossil-users@lists
On 01.11.2015 13:06, Damien Sykes-Pendleton wrote:
> What reasons could Fossil be unable to listen on a certain port and is there
> anything I’m missing that I should be doing to allow it access?
>
Did you check the settings of the Windows Firewall?
--
tsbg
___
On 01/11/15 13:30, Damien Sykes-Pendleton wrote:
> I’m running Windows. I’m not personally running anything on port 80, though I
> get a blank web page (as opposed to a 404 or problem loading error) when I
> visit localhost.
I forget the name of the tool, but in there's a nifty tool for
Windo
Hi Stephan,
I’m running Windows. I’m not personally running anything on port 80, though I
get a blank web page (as opposed to a 404 or problem loading error) when I
visit localhost.
Thanks.
Damien.
From: Stephan Beal
Sent: Sunday, November 01, 2015 12:10 PM
To: Fossil SCM user's discussion
Sub
On Sun, Nov 1, 2015 at 1:06 PM, Damien Sykes-Pendleton <
dam...@dcpendleton.plus.com> wrote:
> “Unable to open listening socket on ports 80”
> My last machine ran the server on port 80 without issue. Port 80 is the
> port that I have forwarded on my router, I tried with the default port and
> it a
Hi,
I have just got myself a new computer and am trying to restart my Fossil
server, but for some reason it comes up with the message:
“Unable to open listening socket on ports 80”
My last machine ran the server on port 80 without issue. Port 80 is the port
that I have forwarded on my router, I t
On Sat, Oct 31, 2015 at 10:19 PM, Matt Welland
wrote:
> On Sat, Oct 31, 2015 at 1:47 PM, Stephan Beal
> wrote:
>
>> On Sat, Oct 31, 2015 at 9:41 PM, Matt Welland
>> wrote:
>>
>>> BTW, to some extent it is ok for fossil to be opinionated software that
>>> strives to dictate how to do your work.
11 matches
Mail list logo