https://docs.ystv.co.uk/api.php?action=feedcontributions&user=Connor.sanders&feedformat=atomYSTV Documentation Wiki - User contributions [en]2024-03-29T10:24:00ZUser contributionsMediaWiki 1.39.4https://docs.ystv.co.uk/index.php?title=Category:GNU-Linux&diff=3356Category:GNU-Linux2021-10-30T15:47:03Z<p>Connor.sanders: Created page with "Category:Software"</p>
<hr />
<div>[[Category:Software]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=CLI&diff=3355CLI2021-10-30T15:46:50Z<p>Connor.sanders: </p>
<hr />
<div>= Overview =<br />
A [https://en.wikipedia.org/wiki/Command-line_interface CLI] (Command Line Interface) is just a means of giving a system instructions using text. While [https://en.wikipedia.org/wiki/Graphical_user_interface GUIs] usually look more intuitive, after some learning curve CLIs are usually faster, less complex and very easy to automate. At YSTV we only really use two different kinds of CLI languages: Powershell (for Windows) and Bash (for Linux).<br />
<br />
=== Windows ===<br />
Windows is not usually managed in a terminal but over the years it adapted certain CLI tools for different purposes. For local system management you usually have [https://en.wikipedia.org/wiki/Cmd.exe cmd.exe] (although [https://github.com/Microsoft/Terminal Windows Terminal] is much better) and for managing [[Active Directory|networks of Windows systems]] you use [https://en.wikipedia.org/wiki/PowerShell Powershell], which lets you manage users and file structures across multiple computers at once. <br />
<br />
=== Linux (and other Unix-based systems) ===<br />
These days it's fairly optional to use the command line in Linux but when you're managing [[Computing: Servers|Linux servers]] it's actually far far better to just learn how to use it, especially thanks to some [https://www.gnu.org/ very good software] designed entirely on a basis of [https://en.wikipedia.org/wiki/Unix_philosophy simplicity and ease of use]. Lookup how to use [https://www.gnu.org/software/bash/ Bash] and some basic programs in [https://www.gnu.org/software/coreutils/manual/html_node/index.html GNU Core Utils] and you'll be able to manage any of our servers without a problem.<br />
<br />
= Using command lines =<br />
=== Scripting ===<br />
An advantage of CLI programs is being able to [https://linuxhint.com/linux-pipe-command-examples/ join them together] and automate long tasks with nothing but a short interpreted script. In YSTV's github we have [https://github.com/ystv/scripts-and-configs Scripts-and-Configs] where we store misc bash scripts and config files.<br />
<br />
=== Arguments and Config ===<br />
Most linux programs have two ways of changing their effect. First, you can send an argument (e.g. "--help" is a standard way of displaying all the options you can give a program) to set certain variables or adjustments when you run a program. Secondly, you can set config files (e.g. [https://linuxhint.com/vimrc_tutorial/ vimrc]) which change how a program works EVERY time you run it.<br />
<br />
Config files usually have a hierarchy to them - just remember that they prioritise the closest config file to the user. So for example you can have '/etc/CONFIG_FILE' (for all users) then '/home/USERNAME/.CONFIG_FILE' (for just one user), the one in the '/home' folder will take priority over the one in '/etc'. Info about where these config files are stored is usually at the bottom of a [https://linux.die.net/man/ man(ual) page] or, if you're using Windows, just google it and it'll likely be in some obscure folder somewhere.<br />
<br />
[[Category:GNU-Linux]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=CLI&diff=3354CLI2021-10-30T15:45:15Z<p>Connor.sanders: </p>
<hr />
<div>= Overview =<br />
A [https://en.wikipedia.org/wiki/Command-line_interface CLI] (Command Line Interface) is just a means of giving a system instructions using text. While [https://en.wikipedia.org/wiki/Graphical_user_interface GUIs] usually look more intuitive, after some learning curve CLIs are usually faster, less complex and very easy to automate. At YSTV we only really use two different kinds of CLI languages: Powershell (for Windows) and Bash (for Linux).<br />
<br />
=== Windows ===<br />
Windows is not usually managed in a terminal but over the years it adapted certain CLI tools for different purposes. For local system management you usually have [https://en.wikipedia.org/wiki/Cmd.exe cmd.exe] (although [https://github.com/Microsoft/Terminal Windows Terminal] is much better) and for managing [[Active Directory|networks of Windows systems]] you use [https://en.wikipedia.org/wiki/PowerShell Powershell], which lets you manage users and file structures across multiple computers at once. <br />
<br />
=== Linux (and other Unix-based systems) ===<br />
These days it's fairly optional to use the command line in Linux but when you're managing [[Computing: Servers|Linux servers]] it's actually far far better to just learn how to use it, especially thanks to some [https://www.gnu.org/ very good software] designed entirely on a basis of [https://en.wikipedia.org/wiki/Unix_philosophy simplicity and ease of use]. Lookup how to use [https://www.gnu.org/software/bash/ Bash] and some basic programs in [https://www.gnu.org/software/coreutils/manual/html_node/index.html GNU Core Utils] and you'll be able to manage any of our servers without a problem.<br />
<br />
= Using command lines =<br />
=== Scripting ===<br />
An advantage of CLI programs is being able to [https://linuxhint.com/linux-pipe-command-examples/ join them together] and automate long tasks with nothing but a short interpreted script. In YSTV's github we have [https://github.com/ystv/scripts-and-configs Scripts-and-Configs] where we store misc bash scripts and config files.<br />
<br />
=== Arguments and Config ===<br />
Most linux programs have two ways of changing their effect. First, you can send an argument (e.g. "--help" is a standard way of displaying all the options you can give a program) to set certain variables or adjustments when you run a program. Secondly, you can set config files (e.g. [https://linuxhint.com/vimrc_tutorial/ vimrc]) which change how a program works EVERY time you run it.<br />
<br />
Config files usually have a hierarchy to them - just remember that they prioritise the closest config file to the user. So for example you can have '/etc/CONFIG_FILE' (for all users) then '/home/USERNAME/.CONFIG_FILE' (for just one user), the one in the '/home' folder will take priority over the one in '/etc'. Info about where these config files are stored is usually at the bottom of a [https://linux.die.net/man/ man(ual) page] or, if you're using Windows, just google it and it'll likely be in some obscure folder somewhere.</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=CLI&diff=3353CLI2021-10-30T15:43:13Z<p>Connor.sanders: Created page with "= Overview = A [https://en.wikipedia.org/wiki/Command-line_interface CLI] (Command Line Interface) is just a means of giving a system instructions using text. While [https://e..."</p>
<hr />
<div>= Overview =<br />
A [https://en.wikipedia.org/wiki/Command-line_interface CLI] (Command Line Interface) is just a means of giving a system instructions using text. While [https://en.wikipedia.org/wiki/Graphical_user_interface GUIs] usually look more intuitive, after some learning curve CLIs are usually faster, less complex and very easy to automate. At YSTV we only really use two different kinds of CLI languages: Powershell (for Windows) and Bash (for Linux).<br />
<br />
=== Windows ===<br />
Windows is not usually managed in a terminal but over the years it adapted certain CLI tools for different purposes. For local system management you usually have [https://en.wikipedia.org/wiki/Cmd.exe cmd.exe] (although [https://github.com/Microsoft/Terminal Windows Terminal] is much better) and for managing [Active Directory|networks of Windows systems]] you use [https://en.wikipedia.org/wiki/PowerShell Powershell], which lets you manage users and file structures across multiple computers at once. <br />
<br />
=== Linux (and other Unix-based systems) ===<br />
These days it's fairly optional to use the command line in Linux but when you're managing [[servers|Computing:Servers]] it's actually far far better to just learn how to use it, especially thanks to some [https://www.gnu.org/ very good software] designed entirely on a basis of [https://en.wikipedia.org/wiki/Unix_philosophy simplicity and ease of use]. Lookup how to use [https://www.gnu.org/software/bash/ Bash] and some basic programs in [https://www.gnu.org/software/coreutils/manual/html_node/index.html GNU Core Utils] and you'll be able to manage any of our servers without a problem.<br />
<br />
= Using command lines =<br />
=== Scripting ===<br />
An advantage of CLI programs is being able to [https://linuxhint.com/linux-pipe-command-examples/ join them together] and automate long tasks with nothing but a short interpreted script. In YSTV's github we have [https://github.com/ystv/scripts-and-configs Scripts-and-Configs] where we store misc bash scripts and config files.<br />
<br />
=== Arguments and Config ===<br />
Most linux programs have two ways of changing their effect. First, you can send an argument (e.g. "--help" is a standard way of displaying all the options you can give a program) to set certain variables or adjustments when you run a program. Secondly, you can set config files (e.g. [https://linuxhint.com/vimrc_tutorial/ vimrc]) which change how a program works EVERY time you run it.<br />
<br />
Config files usually have a hierarchy to them - just remember that they prioritise the closest config file to the user. So for example you can have '/etc/CONFIG_FILE' (for all users) then '/home/USERNAME/.CONFIG_FILE' (for just one user), the one in the '/home' folder will take priority over the one in '/etc'. Info about where these config files are stored is usually at the bottom of a [https://linux.die.net/man/ man(ual) page] or, if you're using Windows, just google it and it'll likely be in some obscure folder somewhere.</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=IRC&diff=3352IRC2021-10-30T14:53:34Z<p>Connor.sanders: Created page with "[http://www.irc.org/ IRC] is a text-based chat client used mostly by Computing Team to talk with either Alumni or specialised groups i..."</p>
<hr />
<div>[http://www.irc.org/ IRC] is a [[CLI|text-based]] chat client used mostly by [[hist:Computing_Directors|Computing Team]] to talk with either [[Alumni]] or specialised groups in different areas of computing (e.g. [https://bitcoin-irc.chaincode.com/bitcoin-core-dev A bitcoin git tracker on IRC]).<br />
<br />
== Overview ==<br />
Unlike other chat clients, IRC doesn't technically have a "history" (making it kind of opposite to things like mailing lists e.g. [https://lkml.org/ the Linux Kernel's mailing list]) - when you connect to a server you will only get the messages sent while that connection is active. <br />
<br />
== How to Get IRC ==<br />
???</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=YSTV_IRC&diff=3351YSTV IRC2021-10-30T14:24:34Z<p>Connor.sanders: Connor.sanders moved page IRC to YSTV IRC without leaving a redirect: Make this page specifically for our IRC, leaving "IRC" to be a general intro/overview of the service</p>
<hr />
<div>YSTV maintains an [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] channel on [[w:Freenode|Freenode]], '''''[irc://irc.freenode.net/ystv #ystv]'''''. The [http://hexchat.github.io/downloads.html HexChat] client is recommended, though you are free to use any you wish. A web client is available at [http://webchat.freenode.net/ webchat.freenode.net]. [https://www.irccloud.com/ IRCCloud] provides a good mobile client, with a week's free trial of permanent connection. YSTV are also credited with the creation of the [[hist:NaSTA|NaSTA]] channel, [irc://irc.freenode.net/nasta #nasta] at the NaSTA North Conference 2014.<br />
<br />
== NickServ ==<br />
It is recommended you register your chosen nickname with [[w:NickServ|NickServ]] in order to prevent impersonation. Type <code>/msg nickserv register <password> <email address></code> to register your name. You'll receive a confirmation email with a code. Once you're registered, upon entering any channel on the same network you can type <code>/msg nickserv identify <password></code> to confirm your identity and boot off anyone using your name.<br />
<br />
== Bots ==<br />
<br />
The channel also plays host to a number of bots, providing monitoring and other features.<br />
<br />
=== Morrissey ===<br />
'''''Morrissey''''' is YSTV's IRC bot, named after [[hist:Morrissey the YSTV stuffed rabbit|Morrissey the YSTV stuffed rabbit]]. Maintained by [[hist:Tom Cheyney|Tom Cheyney]],<ref name="github">[https://github.com/Top-Cat/Morrissey Morrissey on GitHub] (may require permission to view, else 404)</ref> it has many useful functions, and a few fun ones. He also has interactive commands.<br />
<br />
* <code>!weather</code> will pull a summary of the current weather local to YSTV. For more detail, use the [http://weather.elec.york.ac.uk/ Electronics department's live weather page]. <code>!WEATHER</code> does something different entirely.<br />
* <code>!quote <string></code> gets Morrissey to pull a quote from the quotes board. Omit the search string for a completely random quote.<br />
* <code>!coin <number_of_flips></code> gets Morrissey to flip coins for you.<br />
* <code>!time</code> tells you the time according to YSTV.<br />
* <code>!nextevent</code> displays upcoming items in the [[Tarantula|schedule]].<br />
* <code>!flooded</code> provides a bite-sized IRC-based alternative to [http://hasystvfloodedyet.com/ hasystvfloodedyet.com].<br />
* <code>!slap <user></code> provides a YSTV-specific alternative to the IRC /slap command.<br />
* <code>!kill <user></code> gets a bit more violent.<br />
* <code>!cuddle <user></code> seems, on the surface at least, to be an antidote to <code>!kill</code>. Variables by [[hist:Greg Ebdon|Greg Ebdon]].<br />
* <code>!random <user></code> is a special window into the mind of [[hist:Helen Hobin|Helen Hobin]].<br />
<br />
=== Jenkins-ystv ===<br />
<br />
'''''jenkins-ystv''''' is the Jenkins build server bot. <ref>[https://wiki.jenkins-ci.org/display/JENKINS/IRC+Plugin Jenkins IRC Plugin]</ref> It runs on [[Computing:Stream Distribution Server | strm1]] and is started and stopped with the main Jenkins service.<br />
<br />
=== Stream-ystv ===<br />
<br />
'''''stream-ystv''''' watches any RTMP stream it is told to watch, and reports when the stream goes black or silent or stops working. Further commands for control can be found at the Github page. <ref>[https://github.com/YSTV/streamcheck Streamcheck on Github]</ref><br />
<br />
=== Xymon-ystv ===<br />
<br />
'''''xymon-ystv''''' is the Xymon monitoring service bot, reporting any issues that Xymon picks up on. The script has been somewhat modified from its original form, to remove the <code>drop</code> command and anything other than red status'.<br />
<br />
== External Links ==<br />
<references /><br />
<br />
[[Category:Glossary]]<br />
[[Category:Communication]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=MediaWiki:Sidebar&diff=3350MediaWiki:Sidebar2021-10-30T14:21:35Z<p>Connor.sanders: Reverted edits by Connor.sanders (talk) to last revision by Rhys.milling</p>
<hr />
<div>* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** Special:Random|Random page<br />
** helppage|help<br />
** mainsite-url|mainsite<br />
** hist:Main Page|History Wiki<br />
* Teams<br />
** Computing:YSTV Computing|Computing<br />
** YSTV Technical|Technical<br />
* Training<br />
** Computing:Basic Remote Livestreams|Livestreams<br />
** Cameras:Camera Operation|Cameras<br />
** Editing:Manual|Video Editing<br />
* Productions<br />
** OB:Outside Broadcasts|Outside Broadcasts</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=MediaWiki:Sidebar&diff=3349MediaWiki:Sidebar2021-10-30T14:21:15Z<p>Connor.sanders: Attempt to put sitemap on side bar</p>
<hr />
<div>* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** Special:Random|Random page<br />
** helppage|help<br />
** mainsite-url|mainsite<br />
** hist:Main Page|History Wiki<br />
* Teams<br />
** Computing:YSTV Computing|Computing<br />
** YSTV Technical|Technical<br />
* Training<br />
** Computing:Basic Remote Livestreams|Livestreams<br />
** Cameras:Camera Operation|Cameras<br />
** Editing:Manual|Video Editing<br />
* Productions<br />
** OB:Outside Broadcasts|Outside Broadcasts<br />
<br />
<categorytree mode="pages" depth=10 hideroot="on" hideprefix="always" style="clear:right; margin-left:5ex; margin-right:5ex; border:3px solid gray; padding:1ex; background-color:white;">Root</categorytree></div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=The_Clock&diff=3343The Clock2021-10-17T16:12:49Z<p>Connor.sanders: Created page with "The (analogue) clock is an endless source of problems in YSTV. It sits idle on the tv rack, constantly out of sync and flashing its little red light. There are means of "contr..."</p>
<hr />
<div>The (analogue) clock is an endless source of problems in YSTV. It sits idle on the tv rack, constantly out of sync and flashing its little red light. There are means of "controlling it" though they've yet to be proven effective (Ben is working on this). On moss you'll find a script called [https://youtu.be/_0-tWLi0Kp4 "Let there be light"] which streams the correct time over aplay into the clock but may be sending data too fast/slow? For whatever reason it fails.<br />
<br />
There is another clock (digital) in The Studio that works by similar means. Unfortunately we haven't been able to get both working at the same time. This is an ongoing project.<br />
<br />
[[Category:Hardware]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Current_Projects&diff=3315Current Projects2021-08-03T18:51:33Z<p>Connor.sanders: </p>
<hr />
<div>This should be a listing of current, ongoing Technical and Computing projects that aren't yet complete enough to merit real documentation. Be warned, this is liable to be outdated and should be used for some idea of what's going on. Also worth a look is the [https://ystv.co.uk/internal/TechieTodo/ Techie Todo List] and the [https://ystvdev.york.ac.uk/trac Trac Listings] for some of the other ongoing projects.<br />
<br />
If you're interested in any of these projects or want to get involved, feel free to email the person listed under the Responsible heading, bearing in mind all YSTV email addresses are of the firstname.lastname@ystv.co.uk form where another address isn't listed.<br />
<br />
= Ongoing Projects =<br />
<br />
=== Website rebuild ===<br />
'''Responsible:''' [[hist:Rhys Milling] and [[hist:Ben Allen]]<br />
<br />
'''Status:''' In progress<br />
<br />
The old website is a rather difficult php site with very little in terms of an API. The rebuild is an attempt to both separate the site into components (front, back, api, auth and special pages) and make the site more easy to build upon in the future.<br />
<br />
=== Archive Server ===<br />
'''Responsible:''' [[hist:Connor Sanders]]<br />
<br />
'''Status:''' In heavy development<br />
<br />
Write an interface to the Archive server to search for items by name or tag, and retrieve them either by download or to a network drive.<br />
<br />
Update 03/08/2021: This is under major rebuild. Previous system has been gone for some time and new method will be a more general archive to link between any and all resources we have.<br />
<br />
=== Single Sign On ===<br />
'''Responsible:''' [[hist:Rhys Milling]]<br />
<br />
'''Status:''' In Progress<br />
<br />
Modify the wikis, forums, webmail etc so that if a user is logged into the website, they also maintain that login through the other online services without having to enter more credentials. Also, automatically logging in to the website if your are logged in with your [[Server account]] would be good<br />
<br />
Update 10/11/2013: See [[Crowd]]. Rolled out for FSRV directory for all areas except History Wiki.<br />
Update 03/08/2021: In process of being remade for modern systems as 'web-auth' although we do have some fairly well integrated system with the Windows VM's Domain. <br />
<br />
=== Document All The Things! ===<br />
'''Responsible:''' [[hist:Connor Sanders]] and/or/as [[hist:Heads_of_Archives]]<br />
<br />
'''Status:''' In Progress<br />
<br />
Basically, write up documentation on everything YSTV does on here. Big project!<br />
<br />
Update 03/08/2021: Wikis reconfigured and restored. New organisation near complete.<br />
<br />
= Stalled Projects =<br />
=== Continuous Channel/Scheduling Engine ===<br />
'''Responsible:''' WAS [[User:sam.nicholson|Sam Nicholson]] NOW [[hist:Rhys Milling]]<br />
<br />
'''Status:''' Being rebuilt as 'playout' and 'video-transcoder' <br />
<br />
Write a scheduling and automation tool to allow the Scheduler to come up with shows, and autofill idents, trailers and graphical overlays to make us more like a "real" TV channel. Known as [[Tarantula]].<br />
<br />
Update 28/05/2013: Now working enough to be used, tracked at [https://ystv.co.uk/trac/Tarantula]. Won the 2013 NaSTA Technical award.<br />
Update 16/10/2013: Deploying now.<br />
Update 03/08/2021: It's been ~8 years - we're considering doing 24 hour streams as soon as we can - some system like this needs remaking<br />
<br />
= Completed Projects =<br />
<br />
=== OB Stream/Receive ===<br />
'''Responsible:''' [[User:sam.nicholson|Sam Nicholson]]/John Caine<br />
<br />
'''Status:''' Complete<br />
<br />
=== Live Link Laptop ===<br />
'''Responsible:''' [[User:sam.nicholson|Sam Nicholson]]<br />
<br />
'''Status:''' Complete<br />
<br />
=== OB Recording ===<br />
'''Responsible:''' [[User:sam.nicholson|Sam Nicholson]]<br />
<br />
'''Status:''' Complete!<br />
<br />
Write a similar wrapper to the video server one for recording on OBs using the capture cards, along with a client to provide a director with record/stream controls, matrix controls, a running order and potentially internal IRC in one handy window.<br />
<br />
=== External IMAP ===<br />
'''Responsible:''' Alex Williams<br />
<br />
'''Status:''' Complete, could do with How To guide though<br />
<br />
Negotiate with IT Services for an external firewall hole, so that YSTV mailboxes can be read using regular clients or phones from off-campus. At present on-campus works, with this running to completion it's probably worth documenting how to set up external YSTV mail.<br />
<br />
=== PiVT ===<br />
'''Responsible:''' Sam Nicholson<br />
<br />
'''Status:''' Done.<br />
<br />
Create a VT server system using a Raspberry Pi and the on-board HD video decode hardware, which should provide cheap HD VT servers.<br />
<br />
Update 16/10/2013: Deployed (mostly!)<br />
<br />
=== Autocue ===<br />
'''Responsible:''' Robert Walker/Sam Nicholson<br />
<br />
'''Status:''' Complete<br />
<br />
Build an autocue. See [[Autocue#AutoDerp|Autocue]].<br />
<br />
= Scrapped Projects =<br />
<br />
=== Easter Refurb ===<br />
'''Responsible:''' Chris Wall, Greg Ebdon, Liz Pascoe, Mike Chislett, Sam Nicholson, Matt Johnson<br />
<br />
'''Status:''' Scrapped<br />
<br />
Still known as the Easter Refurb, despite that holiday being long gone, the plan was to repaint both studio and control room, re-carpet both and generally make the place look nicer. Sort of a tech project.<br />
<br />
Currently Chris Teeling (ZFM) has provisionally agreed to fix our blinds but put the floor etc on hold for a little while due to the potential to move into a new space. It should be noted this is a very early stage, the idea to move was mooted but nobody has said yes in any way shape or form. The individuals listed above are working on details.<br />
<br />
Update 28/05/2013: Firmly scrapped, however much of the plan may happen in the Summer 2015 refurb of James Nucleus<br />
<br />
Update 24/07/2014: Since being 'firmly scrapped', almost all of these things have been done. New blinds have been fitted, as has a carpet, and the studio has been repainted.<br />
<br />
=== DNS Delegation ===<br />
'''Responsible:''' Alex Williams<br />
<br />
'''Status:''' Scrapped<br />
<br />
In theory YSTV could administer our own DNS server, and delegate the zone IT Services manage for us to be managed directly, potentially with access to LanDB for updating our own machines.<br />
<br />
UPDATE (26/06/13): Not possible in 'men and mice'<br />
<br />
=== Video Server Recording ===<br />
'''Responsible:''' [[User:sam.nicholson|Sam Nicholson]]<br />
<br />
'''Status:''' Scrapped<br />
<br />
Write a wrapper to start and stop the [[Computing:Video Server|Video Server]] recording live shows over the network.<br />
<br />
Update 16/10/2013: Scrapped due to HD upgrade completely changing how this will work<br />
<br />
=== New Muxes ===<br />
'''Responsible:''' Michael Chislett<br />
<br />
'''Status:''' Scrapped<br />
<br />
Build a pair of chainable 8x8 video matrixes, as prototyped for NaSTA 2011. See [[hist:P169_Replacement|the history wiki]] for more.<br />
<br />
Update 26/06/13: Will not work with HD, but might be useful for making for the analogue OB trolley<br />
<br />
Update 28/04/2014: Needs a power supply, and code for controlling the matrix chip writing/finding. So scrapped until someone with enough time can look into it.<br />
<br />
=== Jack/JAAK ===<br />
'''Responsible:''' Michael Chislett<br />
<br />
'''Status:''' Scrapped<br />
<br />
The mother of all abstraction layers for the video and audio paths. JAAK will essentially be the auto-router, with simple monitoring of gear statuses.<br />
Shiny things JAAK will do:<br />
* Cope with instruction (graphic touch screen apps) such as "patch studio 92 to DaVE 4". JAAK then goes off and finds the most suitable routing path (shortest and non-conflicting with existing paths).<br />
* Not need a user manual.<br />
* Poll serial ports for new YVP compatible devices<br />
** auto-initiate them.<br />
* Have an advanced command interface, supporting commands such as DO, WHEN & ON. It will also cope with basic logic and events such as time, and whole system I/O events.<br />
* JAAK will also detects and avoid (it already can) things such as routing loops.<br />
<br />
Update 28/05/2013: Updated status to on-hold pending HD roadmap completion<br />
<br />
Update 28/04/2014: Scrapped as not really required - all routing goes through the one [[Videohub]]<br />
<br />
[[Category:Computing]]<br />
[[Category:Technical]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Template:OldKit&diff=3307Template:OldKit2021-08-03T16:47:29Z<p>Connor.sanders: Clean up "bin pile"</p>
<hr />
<div>{| style="font-size:95%; line-height:1.5em; border: 2px solid rgb(178, 34, 34); border-collapse: collapse; background: none repeat scroll 0% 0% rgb(255, 238, 238); margin:4px 10%; margin-left:auto; margin-right:auto; text-align:center;"<br />
| style="padding: 0.9em;" | {{fff|cancel}} [[hist:Joe Wharfe|Joe Wharfe]] says: "{{{1|I have no idea what this and it probably doesn't exist any more, so don't worry about it too much!}}}"<br>If you have reason to believe this isn't something that ended up in the [[:Category:Bin Pile|Bin Pile]], feel free to remove this tag.<br />
|}<br />
<includeonly>[[Category:Bin Pile]]</includeonly></div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Category:Bin_Pile&diff=3305Category:Bin Pile2021-08-03T16:45:42Z<p>Connor.sanders: Created page with "Here lies everything YSTV once owned or tried to bodge together, but ultimately was thrown out."</p>
<hr />
<div>Here lies everything YSTV once owned or tried to [[hist:bodge|bodge]] together, but ultimately was thrown out.</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Template:OldKit&diff=3304Template:OldKit2021-08-03T16:44:58Z<p>Connor.sanders: </p>
<hr />
<div>{| style="font-size:95%; line-height:1.5em; border: 2px solid rgb(178, 34, 34); border-collapse: collapse; background: none repeat scroll 0% 0% rgb(255, 238, 238); margin:4px 10%; margin-left:auto; margin-right:auto; text-align:center;"<br />
| style="padding: 0.9em;" | {{fff|cancel}} [[hist:Joe Wharfe|Joe Wharfe]] says: "{{{1|I have no idea what this and it probably doesn't exist any more, so don't worry about it too much!}}}"<br>If you have reason to believe this isn't something that ended up in the [[:Category:Bin Pile]], feel free to remove this tag.<br />
|}<br />
<includeonly>[[Category:Bin Pile]]</includeonly></div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Jw2199&diff=3302User:Jw21992021-08-03T16:41:53Z<p>Connor.sanders: Created page with "# REDIRECT hist:Joseph_Wharfe"</p>
<hr />
<div># REDIRECT [[hist:Joseph_Wharfe]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Exim&diff=3281Exim2021-08-03T06:44:53Z<p>Connor.sanders: /* Spam Check */</p>
<hr />
<div>Exim is used as our Mail Transfer Agent (MTA) as part of the [[email]] system, and runs on the [[Ystvweb|webserver]]. It is configured in <code>/etc/exim/exim.conf</code>. <br />
<br />
The [[w:Message transfer agent|MTA]] receives incoming email from external sources (usually the mta.york.ac.uk gateways run by the University), runs some checks on it and routes it to the correct user. In this process it handles delivery to [[Mailing Lists|mailing lists]] and [[aliases]] using a series of redirect routers. As the last step mail is run through the [[Dovecot]] LDA to process user filters and deliver it to user mailboxes.<br />
<br />
Due to the withdrawal of the University's spam and virus filtering on their mail relays in October 2012 (as part of the move to Google Apps), Exim operates spam and virus checking on incoming mail, scanning mail using ClamAV and SpamAssassin when it is first received by the server.<br />
One of Exim's Access Control Lists (ACLs) is acl_check_data, which is run immediately after a message is received by the server, before the sender has disconnected. This ACL performs the virus and spam scans, and adds the results to the message headers.<br />
<br />
Despite the move to Google Apps, we have been assured (like other administrators of legacy email systems in the University) that a small number of MTAs will remain active indefinitely to route our mail.<br />
<br />
== Troubleshooting ==<br />
Exim can be a tricky piece of software to reconfigure, fortunately there are some handy commands to help you. Firstly <code>exim -bt somename@ystv.co.uk</code> will show how Exim will attempt to route mail, good for checking why a user gets no mail or whether forwarding works properly. This will work for any email address, including the mailing lists, however external addresses will just show the mail routing to the University mail servers.<br />
<br />
Another useful one is <code>exim -bh 127.0.0.1</code> which is just like telnetting to the server and sending a mail, except it won't actually send an email, just go through all the other motions to do with permissions and spam/virus checks.<br />
<br />
I got these from this [http://bradthemad.org/tech/notes/exim_cheatsheet.php cheatsheet].<br />
<br />
= Virus Scanning =<br />
ClamAV is configured to run as a daemon, connecting to Exim through a socket at <code>/var/run/clamd.exim/clamd.sock</code> using its default configuration. Exim runs the virus scanner on incoming messages via this socket, and any messages are rejected (with a note in the logfile).<br />
<br />
= Spam Check =<br />
Next, Exim connects to the SpamAssassin daemon (spamd) and passes it the message, where it is scanned against the default set of rules. These assign the message spam points based on contents, senders, headers, white/blacklists and Bayesian statistical analysis. The results of this analysis is added to the message in the form of X-Spam-Score and X-Spam-Report headers, where a message with a spam score > 5 is considered spam and has the X-Spam-Flag: YES header added as well. If a message scores >10 it is currently routed to /var/tmp/quarantine and not delivered to the recipient. This will be used to assess whether mail with a score >10 can be safely rejected outright rather than filling up user's mailboxes.<br />
<br />
SpamAssassin configuration is in <code>/etc/mail/spamassassin/local.cf</code>, which overrides a small number of default configuration options. These overrides change the spam report formatting and has a required_hits line which will change the threshold spam score from 5 for all users. The Bayesian database is updated by [[w:cron|cron]], and the cronjob is in <code>/etc/crontab</code>.<br />
<br />
For a while bayes_journal wasn't updating:<br />
<br />
<blockquote>''Ok, fixed it, looks like bayes_journal is created by the apache user, with group apache and permissions 770, but spamd couldn't write to it as it wasn't a member of apache; I think when I first set it up spamd ended up being the owner of that file, but at some point it got deleted and recreated by apache. Solution: add spamd to the apache group: <code>usermod -aG apache spamd</code>'' - [[User:sam.nicholson|Sam Nicholson]], 21 January 2013</blockquote><br />
<br />
<blockquote>''Same issues as before with /data/spamassassin/bayes_journal but due to various server changes the fix no longer works (no more apache). Temporary solution is to change the folder's permissions to be owned by the spamassassin user trying to access it - but this gets reset every so often. <code>chown -Rv mail bayes_*</code>'' - [[Connor Sanders]], 03 August 2021</blockquote><br />
<br />
[[Category:Email]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Tom.lee&diff=3278User:Tom.lee2021-07-26T13:27:00Z<p>Connor.sanders: Redirected page to hist:Tom Lee</p>
<hr />
<div>#REDIRECT [[hist:Tom Lee]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Sam.willcocks&diff=3277User:Sam.willcocks2021-07-26T13:26:00Z<p>Connor.sanders: Redirected page to hist:Sam Willcocks</p>
<hr />
<div>#REDIRECT [[hist:Sam Willcocks]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Robert.drane&diff=3276User:Robert.drane2021-07-26T13:25:26Z<p>Connor.sanders: Redirected page to hist:Robert Drane</p>
<hr />
<div>#REDIRECT [[hist:Robert Drane]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Michael.cullen&diff=3275User:Michael.cullen2021-07-26T13:24:20Z<p>Connor.sanders: Redirected page to hist:Michael Cullen</p>
<hr />
<div>#REDIRECT [[hist:Michael Cullen]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Michael.chislett&diff=3274User:Michael.chislett2021-07-26T13:24:05Z<p>Connor.sanders: Redirected page to hist:Michael Chislett</p>
<hr />
<div>#REDIRECT [[hist:Michael Chislett]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Matthew.stratford&diff=3273User:Matthew.stratford2021-07-26T13:23:40Z<p>Connor.sanders: Redirected page to hist:Matthew Stratford</p>
<hr />
<div>#REDIRECT [[hist:Matthew Stratford]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Lloyd.wallis&diff=3272User:Lloyd.wallis2021-07-26T13:22:48Z<p>Connor.sanders: Redirected page to hist:Lloyd Wallis</p>
<hr />
<div>#REDIRECT [[hist:Lloyd Wallis]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Kieron.moore&diff=3271User:Kieron.moore2021-07-26T13:22:35Z<p>Connor.sanders: Redirected page to hist:Kieron Moore</p>
<hr />
<div>#REDIRECT [[hist:Kieron Moore]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:John.caine&diff=3270User:John.caine2021-07-26T13:21:59Z<p>Connor.sanders: Redirected page to hist:John Caine</p>
<hr />
<div>#REDIRECT [[hist:John Caine]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Dom.hall&diff=3269User:Dom.hall2021-07-26T13:21:07Z<p>Connor.sanders: Redirected page to hist:Dom Hall</p>
<hr />
<div>#REDIRECT [[hist:Dom Hall]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:David.heaton&diff=3268User:David.heaton2021-07-26T13:20:40Z<p>Connor.sanders: Redirected page to hist:David Heaton</p>
<hr />
<div>#REDIRECT [[hist:David Heaton]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Chris.wall&diff=3267User:Chris.wall2021-07-26T13:19:17Z<p>Connor.sanders: Redirected page to hist:Chris Wall</p>
<hr />
<div>#REDIRECT [[hist:Chris Wall]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Caroline.pv&diff=3266User:Caroline.pv2021-07-26T13:17:44Z<p>Connor.sanders: Redirected page to hist:Caroline Preynat-Viero</p>
<hr />
<div>#REDIRECT [[hist:Caroline Preynat-Viero]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Ben.allen&diff=3264User:Ben.allen2021-07-26T13:16:32Z<p>Connor.sanders: Redirected page to hist:Ben Allen</p>
<hr />
<div>#REDIRECT [[hist:Ben Allen]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Anthony.williams&diff=3263User:Anthony.williams2021-07-26T13:16:19Z<p>Connor.sanders: Redirected page to hist:Anthony Williams</p>
<hr />
<div>#REDIRECT [[hist:Anthony Williams]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Andrew.waddle&diff=3262User:Andrew.waddle2021-07-26T13:15:30Z<p>Connor.sanders: Redirected page to hist:Andrew Waddle</p>
<hr />
<div>#REDIRECT [[hist:Andrew Waddle]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Alize.akturk&diff=3261User:Alize.akturk2021-07-26T13:15:18Z<p>Connor.sanders: Redirected page to hist:Alize Akturk</p>
<hr />
<div>#REDIRECT [[hist:Alize Akturk]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Alex.williams&diff=3260User:Alex.williams2021-07-26T13:15:06Z<p>Connor.sanders: Redirected page to hist:Alex Williams</p>
<hr />
<div>#REDIRECT [[hist:Alex_Williams]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Adam.taylor&diff=3259User:Adam.taylor2021-07-26T13:13:51Z<p>Connor.sanders: Redirected page to hist:Adam Taylor</p>
<hr />
<div>#REDIRECT [[hist:Adam_Taylor]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Adam.birtles&diff=3258User:Adam.birtles2021-07-26T13:13:06Z<p>Connor.sanders: Redirected page to hist:Adam Birtles</p>
<hr />
<div>#REDIRECT [[hist:Adam Birtles]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Matt.johnson&diff=3251User:Matt.johnson2021-07-24T15:58:45Z<p>Connor.sanders: Redirected page to hist:Matt Johnson</p>
<hr />
<div>#REDIRECT [[hist:Matt Johnson]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Steven.perring&diff=3250User:Steven.perring2021-07-24T15:57:24Z<p>Connor.sanders: Redirected page to hist:Steven Perring</p>
<hr />
<div>#REDIRECT [[hist:Steven_Perring]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Greg.ebdon&diff=3249User:Greg.ebdon2021-07-24T15:56:51Z<p>Connor.sanders: Redirected page to hist:Greg Ebdon</p>
<hr />
<div>#REDIRECT [[hist:Greg Ebdon]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Alex.muller&diff=3248User:Alex.muller2021-07-24T15:56:20Z<p>Connor.sanders: Redirected page to hist:Alex Muller</p>
<hr />
<div>#REDIRECT [[hist:Alex_Muller]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Alex.appleton&diff=3247User:Alex.appleton2021-07-24T15:55:30Z<p>Connor.sanders: Redirected page to hist:Alex Appleton</p>
<hr />
<div>#REDIRECT [[hist:Alex_Appleton]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Connor.sanders&diff=3246User:Connor.sanders2021-07-24T15:54:13Z<p>Connor.sanders: Redirected page to hist:Connor Sanders</p>
<hr />
<div>#REDIRECT [[hist:Connor Sanders]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=User:Iain.cooke&diff=3245User:Iain.cooke2021-07-24T15:53:21Z<p>Connor.sanders: Redirected page to hist:Iain Cooke</p>
<hr />
<div>#REDIRECT [[hist:Iain_Cooke]]</div>Connor.sandershttps://docs.ystv.co.uk/index.php?title=Computing_talk:YSTV%27s_home-made_Devices&diff=3243Computing talk:YSTV's home-made Devices2021-07-24T14:48:50Z<p>Connor.sanders: Changed redirect target from Technical:YSTV's home-made Devices to YSTV's home-made Devices</p>
<hr />
<div>#REDIRECT [[YSTV's home-made Devices]]</div>Connor.sanders