FYI, for when you get back and have a chance.

==== Changing a user's Security Level ====

At present this must be done with an sqlite utility, for the sqlite3
command line utility:

update users set seclevel=99 where loginname LIKE "apam";


Should read:

==== Changing a user's Security Level ====

At present this must be done with an sqlite utility, for the sqlite3
command line utility:

update users set sec_level=99 where loginname LIKE "apam";

sec_level has an underscore in it.

Might also want to include a note about issuing an ".open users.sq3"
first, or sqlite3 won't be able to find the "users" table. :)

Hope you are enjoying your trip!




--- MagickaBBS v0.13alpha (Linux/armv7l)
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

update users set seclevel=99 where loginname LIKE "apam";

Should read:

update users set sec_level=99 where loginname LIKE "apam";

Ah, good catch. I've tried adjusting sec_level with no success. I don't remember why it failed but I'll try again with sec_level.

Might also want to include a note about issuing an ".open users.sq3" first, or sqlite3 won't be able to find the "users" table. :)

That might be part of my problem too.. thanks for the update.. :)

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Al wrote to Blue White <=-

update users set seclevel=99 where loginname LIKE "apam";

Should read:

update users set sec_level=99 where loginname LIKE "apam";

Ah, good catch. I've tried adjusting sec_level with no success. I don't remember why it failed but I'll try again with sec_level.

Actually, I don't know if it is required or not but, when I had success, I
also put a space before and after the equal sign, i.e. sec_level = 99. I forgot to add the spaces when I copied and changed the line from the docs.

Might also want to include a note about issuing an ".open users.sq3" first, or sqlite3 won't be able to find the "users" table. :)

That might be part of my problem too.. thanks for the update.. :)

It is possible that .open statement is not required, but I sure needed it
here to get sqlite3 to find the table.



... Computer Hacker wanted. Must have own axe.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Thanks for that catch.

Might also want to include a note about issuing an ".open users.sq3" first, or sqlite3 won't be able to find the "users" table. :)

That's only necessary if you don't open it from the command line. Ie
sqlite3 users.sq3 rather than just sqlite3. At any rate I hope to have a utility for seclevels soon.

Hope you are enjoying your trip!

Yep thanks spent today in Adelaide with sister nephew and mum. Tomorrow
going to mum's house which is about 4 and a half hour drive.

Andrew




--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

apam wrote to Blue White <=-

Might also want to include a note about issuing an ".open users.sq3" first, or sqlite3 won't be able to find the "users" table. :)

That's only necessary if you don't open it from the command line. Ie sqlite3 users.sq3 rather than just sqlite3. At any rate I hope to have
a utility for seclevels soon.

Ahhhhh... lol, that would have helped! :)

Hope you are enjoying your trip!

Yep thanks spent today in Adelaide with sister nephew and mum. Tomorrow going to mum's house which is about 4 and a half hour drive.

Sounds like a good time so far.

I am looking forward to a much shorter trip than that, in a couple of
weeks, to see family. It is a "food" holiday so it should be nice. :D


... 2 + 2 = 5 for extremely large values of 2.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)