I copied the mystic binary file from 2018/04/11 back into the directory, and it seems to be running fine again. It may just be something with the compiler settings...
I copied the mystic binary file from 2018/04/11 back into the directo and it seems to be running fine again. It may just be something with compiler settings...
Or you know, an access problem on your end :)
When I install the newer pre-alpha versions into a temp directory, I can run ./mystic -ver, and it works with no problems. Once the executable is copied into the /mystic directory, it will only give me 'Access denied'.
On 04/14/18, g00r00 said the following...
I copied the mystic binary file from 2018/04/11 back into the di and it seems to be running fine again. It may just be something compiler settings...
Or you know, an access problem on your end :)
I hope this is all it is...
When I install the newer pre-alpha versions into a temp directory, I can run ./mystic -ver, and it works with no problems. Once the executable is copied into the /mystic directory, it will only give me 'Access denied'.
I've checked, and all the files in the /mystic directory are owned by my linux user. I made sure the file is set as executable. I've even tried running the ./upgrade again, and it states that all the files are up to date.
This has only been with any of the pre-alphas after the 2018/04/11 version.
ls -la mystic
-rwxrwxrwx 1 dan dan 1071552 Apr 14 21:41 mystic
I know I'm still relatively new to Linux, but what am I missing? I'm
On 04/14/18, g00r00 said the following...
I copied the mystic binary file from 2018/04/11 back into the di and it seems to be running fine again. It may just be something compiler settings...
Or you know, an access problem on your end :)
I hope this is all it is...
When I install the newer pre-alpha versions into a temp directory, I can run ./mystic -ver, and it works with no problems. Once the executable is copied into the /mystic directory, it will only give me 'Access denied'.
I've checked, and all the files in the /mystic directory are owned by my linux user. I made sure the file is set as executable. I've even tried running the ./upgrade again, and it states that all the files are up to date.
This has only been with any of the pre-alphas after the 2018/04/11 version.
I can confirm this the quick fix was to chmod +x mystic.dat for some reason which I never had to do before? But it got my BBS back online without me having to change versions back.
I can confirm this the quick fix was to chmod +x mystic.dat for some reason which I never had to do before? But it got my BBS back online without me having to change versions back.
v1.12 A39 Linux/64 Compiled 2018/04/14 22:10:34
I can confirm this the quick fix was to chmod +x mystic.dat for some reason which I never had to do before? But it got my BBS back online without me having to change versions back.
It worked! :) Great job!
On 04/15/18, Pequito said the following...
I can confirm this the quick fix was to chmod +x mystic.dat for some reason which I never had to do before? But it got my BBS back online without me having to change versions back.
It worked! :) Great job!
I can confirm this the quick fix was to chmod +x mystic.dat for reason which I never had to do before? But it got my BBS back o without me having to change versions back.
It worked! :) Great job!
No prob, making me wonder why that file needs to have those permissions
When I install the newer pre-alpha versions into a temp directory, I can run ./mystic -ver, and it works with no problems. Once the executable is copied into the /mystic directory, it will only give me 'Access denied'.
Black Panther wrote to Pequito <=-
On 04/15/18, Pequito said the following...
I can confirm this the quick fix was to chmod +x mystic.dat for some
I never would have thought to do that... I'm gonna try it now.
Pequito wrote to Black Panther <=-
No prob, making me wonder why that file needs to have those permissions though. heh =P
When I install the newer pre-alpha versions into a temp directory, I run ./mystic -ver, and it works with no problems. Once the executable copied into the /mystic directory, it will only give me 'Access denie
I had a chance to take a look into things and you probably have to +X to mystic.dat in the build of the pre-alpha you have. Or you can upgrade
to the latest build and not do anything.
I can confirm this the quick fix was to chmod +x mystic.dat for some
I never would have thought to do that... I'm gonna try it now.
Yes, whenever I get "Permission denied", I look for both correct permissions and whether the binaries or scripts I need are actually executable.
Pequito wrote to Black Panther <=-
No prob, making me wonder why that file needs to have those permissio though. heh =P
Probably always needed it, but for some reason, stored in an archive without them? :)
Pequito actually figured it out, and it seems to work fine. :)
Is there a newer pre-alpha already? I've got 04/14 22:10:34 running now.
Black Panther wrote to Vk3jed <=-
If the error was 'Permission denied', I would have looked at the permissions, but this one was actually 'Access denied'. I was checking everything, except making the mystic.dat file executable...
It's working now, so we're good. ;)
Pequito wrote to Vk3jed <=-
Probably always needed it, but for some reason, stored in an archive without them? :)
Nope was the 1st time I had to change permissions for it, also g00r00 mentioned in the next one this is resolved/fixed.
At this point I am shooting for a Friday A39 release. Time to get that
Pi fired up again! :)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 2 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 115:42:12 |
| Calls: | 2,127 |
| Calls today: | 3 |
| Files: | 11,149 |
| D/L today: |
41 files (21,471K bytes) |
| Messages: | 950,877 |