Guardian BBS Activity
Brought to you by:
azazel-az
Activity for Guardian BBS
-
Flavio Bessa posted a comment on ticket #3
Hello, At the end of the day the issue was not related to permissions. I managed to fix it after comparing the "Archive Editor" with the official Mystic release, then I realized that the zip/unzip commands were lacking quotation marks where the %1 and %2 parameters were. Upon fixed this, the issue was solved.
-
drwxrwxr-x 2 root guardian 4096 Dec 28 05:48 localqwk drwxrwxr-x 2 root guardian 4096 Mar 7 08:14 logs -rwxrwxrwx 1 root guardian 16735 Mar 7 08:15 mailin.ini -rwxrwxrwx 1 root guardian 16744 Feb 26 17:09 mailout.ini -rwxrwxr-x 1 root guardian 48720 Mar 7 06:06 maketheme drwxrwxr-x 2 root guardian 4096 Feb 26 16:55 menus -rwxrwxr-x 1 root guardian 194448 Mar 7 06:06 mide -rwxrwxr-x 1 root guardian 542832 Mar 7 06:06 mis -rwxrwxr-x 1 root guardian 117824 Mar 7 06:06 mplc drwxrwxr-x 2 root guardian...
-
Hello, I did the changes and the issue continues. When running under flbessa: An unhandled exception occurred at $0000000000400C68 : EInOutError : Access denied $0000000000400C68 When running under sudo: unzip: cannot find zipfile directory in one of /opt/guardian/echomail/in/00000002.mo0 or /opt/guardian/echomail/in/00000002.mo0.zip, and cannot find /opt/guardian/echomail/in/00000002.mo0.ZIP, period.
-
Vincent Chapman modified a comment on ticket #3
Sorry for the delayed response. I do not believe this is a software problem. The reason the packages are not imported is that you do not have permission to write to that folder. The directory listing you posted also shows username in the prompt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo...
-
Sorry for the delayed response. I do not believe this is a software problem. The reason the packages are not imported is that you do not have permission to write to that folder. The directory listing you posted also shows username in the prompt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo...
-
Sorry for the delayed response. I do not believe this is a software problem. The reason the packages are not imported is that you do not have permission to write to that folder. The directory listing you posted also shows username in the prompt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo...
-
Sorry for the delayed response. I do not believe this is a software problem. The directory listing you posted also shows username in the prompt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo add flbessa guardian then change permission for flbessa to access guardian. This BBS was ported origially...
-
Sorry for the delayed response. I do not believe this is a software problem. The directory listing you posted also shows username in the promt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo add flbessa guardian then change permission for flbessa to access guardian. This BBS was ported origially...
-
Sorry for the delayed response. I do not believe this is a software problem. The directory listing you posted also shows username in the promt, which is very helpful in rapidly diagnosising the problem. If you review the permission, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo add flbessa guardian then change permission for flbessa to access guardian. This BBS was ported origially from the microsoft world, and...
-
Sorry for the delayed response. I do not believe this is a software problem. The directory listing you posted also shows username in the promote. If you review the permission, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group $ sudo add flbessa guardian then change permission for flbessa to access guardian. This BBS was ported origially from the microsoft world, and the error messages may not correcly reflect permission problems....
-
Please find attached the scripts I am using for importing and exporting messages...
-
QWK packages are empty
-
Essentially, you can see the following error messages when running mutil: unzip:...
-
-
That's the error message I get: An unhandled exception occurred at $0000000000400C68...
-
MUTIL fails upon importing messages
-
MUTIL fails upon executing
-
mutil 'guardian.dat not found' fixed
-
Code is fixed, bug is fixed. .deb file is updated and can be installed with dpkg
-
Guardian BBS released /v2.0 A01/guardian-bin.amd64.2017.03.07.deb
-
Root committed [b663a4]
Fixed mutil guardian.dat bug
-
Filename is wrong in souce code for mutil. For now, until I can update the code,...
-
MUTIL fails upon executing
-
-
removed remd out unused code
-
-
-
fixed core to all arch
-
-
-
-
-
-
further cleaned up build/package scriprs
-
data files
-
added installer back into deb file
-
moved guardian/guardian to guardian/src
-
removed duplicate files
-
got login copyrights looking nice
-
-
fixed, build were happening from wrong directory
-
cleaned up .deb scripts some
-
-
-
-
removed some old stuff from build-bbs
-
-
-
removed old git info causing problems
-
moved bbs ident prior to system password
-
fixed some copyright info
-
-
-
add src folders
-
fix
-
Initial commit
1
