From tpg at ucc.asn.au Wed May 4 12:49:11 2016 From: tpg at ucc.asn.au (tpg at ucc.asn.au) Date: Wed, 04 May 2016 12:49:11 +0800 Subject: [tech] New Machines - Chubsucker and Caan Message-ID: Hello All! The new machines were built last Thursday, and had the Mint SOE installed on Friday. "caan" has replaced everyone's favourite machine "cockgrunter", and seems to be going well. The other new machine "chubsucker" is currently sitting next to caan. (And eventually will replace porcupine). They're standard installs except for two points 1. The drivers for the nvidia 960 chipset are not in the Mint/Ubuntu official repositories, so a PPA has been used (ppa:graphics-drivers/ppa) - Both the new machines, and pinball (which has the same graphics chipset) have this PPA 2. The new machines are running a nightly version of the ALSA drivers (oem-audio-hda-daily-lts-vivid-dkms - 0.201605032232~ubuntu14.04.1) because the audio chipset is too new for the version packaged with Ubuntu 14.04, which is what Mint 17.3 is based on. John Hodge [TPG] UCC Wheel Member From vanbujm at gmail.com Tue May 17 14:15:26 2016 From: vanbujm at gmail.com (Jonathan Van buren) Date: Tue, 17 May 2016 06:15:26 +0000 Subject: [tech] UCC database Message-ID: Hey all, Got a question. What type of database (if any) does ucc use to store all the members user account information? How accessible is this information (I know you can finger system accounts can you also query the database for information or do you need elevated privileges to do so)? I am planning a tech talk on web dev and wanted to see what information ucc has that could be manipulated as a demonstration. Thanks <3 JVB -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ucc.gu.uwa.edu.au/pipermail/tech/attachments/20160517/98dcc259/attachment.htm From zanchey at ucc.gu.uwa.edu.au Sun May 22 05:17:58 2016 From: zanchey at ucc.gu.uwa.edu.au (David Adam) Date: Sun, 22 May 2016 05:17:58 +0800 (AWST) Subject: [tech] UCC database In-Reply-To: References: Message-ID: On Tue, 17 May 2016, Jonathan Van buren wrote: > Got a question. What type of database (if any) does ucc use to store all > the members user account information? How accessible is this information (I > know you can finger system accounts can you also query the database for > information or do you need elevated privileges to do so)? As far as I know, there's two different sources of information. The authoritative database for account information - that is, user names, passwords, Unix and Windows user IDs, home directories and so on - is stored in our OpenLDAP server and accessed via LDAP. You do need elevated privileges to view some information such as password hashes, but you can have a look at what's stored as an anonymous user: $ ldapvi '(uid=*)' This will show you the entries for all users on the system (use plain `ldapvi` to look through the entire database, but there is lots of other uninteresting system information inside). However, the membership register - which contains full names, addresses, student numbers and so on - is maintained separately. At the moment I think we're still using MemberDB, which [PXY] started and I continued with, renamed as the Gumby Management System (after the Fish Management System, an old machine database at UCC - after all G follows F :-). This is accessible at: https://secure.ucc.asn.au/members/ You do need to be on committee (or have committee add you) as obviously this information is private. GMS is written in a Python framework called Django, and the thing about it that made it so suitable is that the entire thing is under 100 lines of code and configuration. You can have a look at the source, I think - it's in /services/gms with the bulk of the code in /services/gms/memberdb/models.py. This sits on top of a PostgreSQL database, although that's entirely an implementation detail - in the past it was a SQLite database in the secretary's home directory. There have been plans for years to merge these two databases, or to rewrite MemberDB/GMS into something bigger that would allow online signups or even payments. The former is a bad idea - we need to keep historical records and carefully protect the privacy of the information, and OpenLDAP makes this easy to mess up. The latter is a great idea, but it's quite hard and involves words like "workflow" which are no fun. David Adam zanchey@ From vanbujm at gmail.com Sun May 22 10:47:58 2016 From: vanbujm at gmail.com (Jonathan Van buren) Date: Sun, 22 May 2016 02:47:58 +0000 Subject: [tech] UCC database In-Reply-To: References: Message-ID: Great, thanks! I shall investgate further, but that is exactly the information I needed. On Sun, 22 May 2016 at 05:18 David Adam wrote: > On Tue, 17 May 2016, Jonathan Van buren wrote: > > Got a question. What type of database (if any) does ucc use to store all > > the members user account information? How accessible is this information > (I > > know you can finger system accounts can you also query the database for > > information or do you need elevated privileges to do so)? > > As far as I know, there's two different sources of information. > > The authoritative database for account information - that is, user names, > passwords, Unix and Windows user IDs, home directories and so on - is > stored in our OpenLDAP server and accessed via LDAP. You do need elevated > privileges to view some information such as password hashes, but you can > have a look at what's stored as an anonymous user: > > $ ldapvi '(uid=*)' > > This will show you the entries for all users on the system (use plain > `ldapvi` to look through the entire database, but there is lots of other > uninteresting system information inside). > > However, the membership register - which contains full names, addresses, > student numbers and so on - is maintained separately. At the moment I > think we're still using MemberDB, which [PXY] started and I continued > with, renamed as the Gumby Management System (after the Fish Management > System, an old machine database at UCC - after all G follows F :-). > > This is accessible at: > https://secure.ucc.asn.au/members/ > > You do need to be on committee (or have committee add you) as obviously > this information is private. > > GMS is written in a Python framework called Django, and the thing about it > that made it so suitable is that the entire thing is under 100 lines of > code and configuration. You can have a look at the source, I think - it's > in /services/gms with the bulk of the code in > /services/gms/memberdb/models.py. > > This sits on top of a PostgreSQL database, although that's entirely an > implementation detail - in the past it was a SQLite database in the > secretary's home directory. > > There have been plans for years to merge these two databases, or to > rewrite MemberDB/GMS into something bigger that would allow online signups > or even payments. The former is a bad idea - we need to keep historical > records and carefully protect the privacy of the information, and OpenLDAP > makes this easy to mess up. The latter is a great idea, but it's quite > hard and involves words like "workflow" which are no fun. > > David Adam > zanchey@ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ucc.gu.uwa.edu.au/pipermail/tech/attachments/20160522/8567d645/attachment.htm From oxinabox at ucc.asn.au Mon May 23 11:44:25 2016 From: oxinabox at ucc.asn.au (oxinabox at ucc.asn.au) Date: Mon, 23 May 2016 11:44:25 +0800 Subject: [tech] UCC database In-Reply-To: References: Message-ID: <87c9540272dc39ce595450590e3aee47@ucc.asn.au> At one point I listed out the secondary information stores. There it the Coke database, that stores all the information about dispense, plus whether or not people are on door. There is a flat-file listing all lifemembers. The TLA's are stored in a *almost* flat-file -- but easier to query via the tla script. I think there are quiet a few others. Eg everyone's email forwarding address is in there .forward file. (Which may disagree with the email in memberdb) [*OX] On 22.05.2016 10:47, Jonathan Van buren wrote: > Great, thanks! > I shall investgate further, but that is exactly the information I > needed. > > On Sun, 22 May 2016 at 05:18 David Adam > wrote: > >> On Tue, 17 May 2016, Jonathan Van buren wrote: >>> Got a question. What type of database (if any) does ucc use to >> store all >>> the members user account information? How accessible is this >> information (I >>> know you can finger system accounts can you also query the >> database for >>> information or do you need elevated privileges to do so)? >> >> As far as I know, there's two different sources of information. >> >> The authoritative database for account information - that is, user >> names, >> passwords, Unix and Windows user IDs, home directories and so on - >> is >> stored in our OpenLDAP server and accessed via LDAP. You do need >> elevated >> privileges to view some information such as password hashes, but you >> can >> have a look at what's stored as an anonymous user: >> >> $ ldapvi '(uid=*)' >> >> This will show you the entries for all users on the system (use >> plain >> `ldapvi` to look through the entire database, but there is lots of >> other >> uninteresting system information inside). >> >> However, the membership register - which contains full names, >> addresses, >> student numbers and so on - is maintained separately. At the moment >> I >> think we're still using MemberDB, which [PXY] started and I >> continued >> with, renamed as the Gumby Management System (after the Fish >> Management >> System, an old machine database at UCC - after all G follows F :-). >> >> This is accessible at: >> https://secure.ucc.asn.au/members/ [1] >> >> You do need to be on committee (or have committee add you) as >> obviously >> this information is private. >> >> GMS is written in a Python framework called Django, and the thing >> about it >> that made it so suitable is that the entire thing is under 100 lines >> of >> code and configuration. You can have a look at the source, I think - >> it's >> in /services/gms with the bulk of the code in >> /services/gms/memberdb/models.py. >> >> This sits on top of a PostgreSQL database, although that's entirely >> an >> implementation detail - in the past it was a SQLite database in the >> secretary's home directory. >> >> There have been plans for years to merge these two databases, or to >> rewrite MemberDB/GMS into something bigger that would allow online >> signups >> or even payments. The former is a bad idea - we need to keep >> historical >> records and carefully protect the privacy of the information, and >> OpenLDAP >> makes this easy to mess up. The latter is a great idea, but it's >> quite >> hard and involves words like "workflow" which are no fun. >> >> David Adam >> zanchey@ > > > Links: > ------ > [1] https://secure.ucc.asn.au/members/ > > _______________________________________________ > List Archives: http://lists.ucc.gu.uwa.edu.au/pipermail/tech > > Unsubscribe here: > http://lists.ucc.gu.uwa.edu.au/mailman/options/tech/oxinabox%40ucc.asn.au From oxinabox at ucc.asn.au Thu May 26 13:35:43 2016 From: oxinabox at ucc.asn.au (Frames) Date: Thu, 26 May 2016 13:35:43 +0800 Subject: [tech] Something wrong with thedom102's /away directory Message-ID: <57468B2F.9080703@ucc.asn.au> Hey, there is something wrong with thedom102's /away directory. In particular root doesn't seem to be able to read: `/away/ucc/thedom102/Documents` Anyone got any idea what is going on with it? Running directly on molmol seems to work, but then freezes the whole session suddenly when in the directory (probably on tabcompletion trying to read a directory). Ben has been having these issues for a while, I recall TPG found and fixed something a while back. I'm spending a bit of time debugging but I got to go do work very soon. Anyone got bright ideas? Regards [*OX] From tpg at ucc.asn.au Thu May 26 22:40:23 2016 From: tpg at ucc.asn.au (John Hodge) Date: Thu, 26 May 2016 22:40:23 +0800 Subject: [tech] Something wrong with thedom102's /away directory In-Reply-To: <57468B2F.9080703@ucc.asn.au> References: <57468B2F.9080703@ucc.asn.au> Message-ID: The issues I found were with some user's windows profile directories, and the solution was to isolate the bad directory and move it out of the way (or to recreate the windows profile). Both were just workarounds. The same workaround could be done here (at least for now). On 26/05/2016 1:35 PM, Frames wrote: > Hey, > there is something wrong with thedom102's /away directory. > > In particular root doesn't seem to be able to read: > `/away/ucc/thedom102/Documents` > > Anyone got any idea what is going on with it? > > Running directly on molmol seems to work, but then freezes the whole > session > suddenly when in the directory (probably on tabcompletion trying to read > a directory). > > Ben has been having these issues for a while, > I recall TPG found and fixed something a while back. > > I'm spending a bit of time debugging but I got to go do work very soon. > Anyone got bright ideas? > > Regards > [*OX] > _______________________________________________ > List Archives: http://lists.ucc.gu.uwa.edu.au/pipermail/tech > > Unsubscribe here: http://lists.ucc.gu.uwa.edu.au/mailman/options/tech/tpg%40ucc.gu.uwa.edu.au