On 27/02/16 16:15, Robert McWilliam wrote:
I'd look at what other functions are in the systemd.sh script, search
the other scripts for places they're called and make sure the logic
around that will pick the systemd option. Robert
Hi Robert ... I've just sent the below to the Symform team. I
On 27/02/16 16:15, Robert McWilliam wrote:
I'd look at what other functions are in the systemd.sh script, search
the other scripts for places they're called and make sure the logic
around that will pick the systemd option. Robert
Hi Robert I thought the easiest thing would be to
As Robert says, the installation process has failed as it assumed that
initctl was there and probably created an upstart service but as initctl
isn't available it won't work, so it's probably a case of converting the
upstart service to systemctl, which I'm sure is possible but I don't know
how off
On Sat, Feb 27, 2016, at 15:53, Barry Drake wrote:
> Hi Simon The 'start' command in the systemd.sh script is:
> start_service()
> {
> systemctl start symform${1}.service
> }
>
> systemctl is very different in its operation. The 'start' command won't
> listen to a port. There
On 26/02/16 20:27, Simon Greenwood wrote:
That's the answer - there should be. There will be something in the
scripts that activates it. If you don't know, 127.0.0.1 is localhost,
your own computer, so it will always ping but it's unlikely that you
have anything running on it in normal use so
As it says, initctl is part of upstart, which has been deprecated for
systemd. However, the components are still there so the script's criteria
are met apart from initctl not being installed. You could comment out the
first if statement in the platform script and replace the 'elif' at the
start of
On 26/02/16 20:27, Simon Greenwood wrote:
That's the answer - there should be. There will be something in the
scripts that activates it. If you don't know, 127.0.0.1 is localhost,
your own computer, so it will always ping but it's unlikely that you
have anything running on it in normal use so
On 26/02/16 20:37, Barry Drake wrote:
Hi Simon I didn't know that. Looks like I have a few more
scripts to look through.
Hi Simon I've just found
http://linux-commands-examples.com/initctl It seems it isn't deprecated
- just missing from recent Ubuntu releases. I'll see if I
On 26/02/16 20:37, Barry Drake wrote:
Hi Simon I didn't know that. Looks like I have a few more
scripts to look through. There are a fair few of them. I might fire
up 14.04 again tomorrow and see what's happening on port 59234.
I've found out exactly where the problem exists. I've put
On 26/02/16 20:27, Simon Greenwood wrote:
That's the answer - there should be. There will be something in the
scripts that activates it. If you don't know, 127.0.0.1 is localhost,
your own computer, so it will always ping but it's unlikely that you
have anything running on it in normal use so
That's the answer - there should be. There will be something in the scripts
that activates it. If you don't know, 127.0.0.1 is localhost, your own
computer, so it will always ping but it's unlikely that you have anything
running on it in normal use so it won't respond to a HTTP request in a web
On 26/02/16 18:21, Simon Greenwood wrote:
It looks like there should be something listening on port 59234, which
you should be able to identify from sudo netstat -nlp. My guess is
that it's an ssh tunnel if the application is bash based. It may not
have been shut down previously or there might
It looks like there should be something listening on port 59234, which you
should be able to identify from sudo netstat -nlp. My guess is that it's an
ssh tunnel if the application is bash based. It may not have been shut down
previously or there might be something else on that port.
On 26
Hi Any pointer for me in trying to solve a problem. When I attemp
to install the Symform cloud software, on 15.04, when it makes a call
to 127.0.0.1:59234 to register the user, Firefox comes up with a "Unable
to connect Firefox can't establish a connection to the server at
Hi there ... Got a weird problem in Trusty. When booting, I get to the
login screen and find I have no keyboard at quite random intervals. It
boots properly an most occasions, then boots with the problem. If I get
up a terminal, the keyboard works, so this is something to do with 'X' I
@google hope you enjoyed reading this, It had nothing to do with you!
sent from my HTC.
On Dec 15, 2013 10:48 AM, Barry Drake ubuntu-advertis...@gmx.com wrote:
Hi there ... Got a weird problem in Trusty. When booting, I get to the
login screen and find I have no keyboard at quite random
On 15/12/13 11:43, Pete Smout wrote:
Don't know if its linked but for some unknown reason my 13.10 keeps
going to American keyboard layout, event though the default is UK! No
pattern and easy fix but seem strange we should both have keyboard
related issue that shows its face randomly!
No -
On 15 December 2013 11:43, Pete Smout smoutp...@gmail.com wrote:
Don't know if its linked but for some unknown reason my 13.10 keeps going to
American keyboard layout, event though the default is UK! No pattern and
easy fix but seem strange we should both have keyboard related issue that
shows
Hi there
Wondered if anyone has any thoughts on this. I'm running Lucid on a
Dell Inspiron Mini v10. Every 10th or so re-boot, it seems to carry out
a forced disk check. I don't know if it's relevant, but it has an SSD
drive which I formatted ext2 on the advice on an Ubuntu forum as
On Monday 19 Apr 2010 16:31:10 Barry Drake wrote:
Hi there
Wondered if anyone has any thoughts on this. I'm running Lucid on a
Dell Inspiron Mini v10. Every 10th or so re-boot, it seems to carry out
a forced disk check. I don't know if it's relevant, but it has an SSD
drive which I
Mark Fraser wrote:
Take a look at this bug and its duplicates on launchpad
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/554737 .
Thanks for that. This is definitely the same bug, and it explains a
whole lot of things I'm seeing. I know where to look now. Plymouth has
repeatedly
21 matches
Mail list logo
