What's the specific OS & version?
Are you launching LinuxCNC manually after the system comes up, or
automatically at startup via systemd (or initd or ???)?
For systemd, try: systemd-analyze <linuxcnc.servicename>
If you're launching manually, dig into your log files and use tools line
strace to see what's going on behind the scenes.
...and if you don't have a network connection to the internet, make sure
you disable all startup services (like ntp) that require internet
connectivity to function or configure them to use only local network
resources (perhaps "tick.localnetwork.com" or similar).
On 6/3/2024 10:54 AM, Jon Elson wrote:
I have several special-purpose devices based on machinekit on the
Beagle Bone.
In one case, we are using it in a hospital where they won't allow us
to connect anything to their network. So, we set up a point to point
Ethernet link between a laptop and the Beagle Bone. When starting
LinuxCNC, there is a HUGE delay of about 10 minutes before the Axis
GUI comes up. I think I have traced it to be caused by there being no
NTP time server. I think we see the same delay with either a Linux or
Windows computer used to access the Beagle.
Does this ring a bell with anyone? Is there a workaround? (Process to
kill or needs to be run?)
Thanks for any hints,
Jon
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
--
Charles Steinkuehler
char...@steinkuehler.net
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
