Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-04-17

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:13 censorsh1 joined #salt
00:18 x409 joined #salt
00:27 edrocks joined #salt
00:29 Tanta joined #salt
00:34 leonkatz joined #salt
00:47 justan0theruser joined #salt
01:00 jdipierro joined #salt
01:12 catpiggest joined #salt
01:30 DEger joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.3 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ (please don't multiline paste into channel) <+> See also: #salt-devel, #salt-offtopic <+> Ask with patience as we are volunteers and may not have immediate answers
01:50 scoates joined #salt
01:54 coldbrewedbrew joined #salt
01:54 coldbrewedbrew joined #salt
01:54 coldbrewedbrew_ joined #salt
01:55 FreeSpencer joined #salt
01:55 FreeSpencer joined #salt
02:01 jas02 joined #salt
02:20 ujjain joined #salt
02:20 ujjain joined #salt
02:24 justanotheruser joined #salt
02:29 asyncsec joined #salt
02:46 JPT joined #salt
03:05 Tanta joined #salt
03:33 armyriad joined #salt
03:42 evle joined #salt
03:44 armguy joined #salt
03:58 catpiggest left #salt
04:07 djgerm joined #salt
04:09 jas02 joined #salt
04:40 rdas joined #salt
05:06 DEger joined #salt
05:08 preludedrew joined #salt
05:10 DEger joined #salt
05:39 ProT-0-TypE joined #salt
05:53 nick123 joined #salt
05:57 DEger joined #salt
05:58 Inveracity joined #salt
06:33 ReV013 joined #salt
06:36 jas02 joined #salt
06:48 mk-fg joined #salt
06:48 mk-fg joined #salt
06:51 misconfig joined #salt
07:10 auzty joined #salt
07:33 theblazehen joined #salt
07:42 jas02 joined #salt
08:37 Mattch joined #salt
09:05 theblazehen joined #salt
09:08 systeem joined #salt
09:14 mikecmpbll joined #salt
09:15 jas02 joined #salt
09:18 Straphka joined #salt
09:32 cyteen joined #salt
09:45 sjorge joined #salt
10:00 Vinod joined #salt
10:00 Vinod Hello,
10:01 Vinod I am new to salt stack, my requirement is to bring up an application server through a state file. It might sound silly to ask a very basic question, but looking for some help.
10:03 jas02 joined #salt
10:04 aldevar joined #salt
10:06 sjorge joined #salt
10:15 Vinod joined #salt
10:15 sjorge joined #salt
10:28 DEger joined #salt
10:41 candyman88 joined #salt
10:42 Praematura joined #salt
10:44 sjorge joined #salt
11:06 systeem joined #salt
11:14 jas02 joined #salt
11:17 hoonetorg joined #salt
11:19 hoonetorg joined #salt
11:56 evle1 joined #salt
11:58 theblazehen joined #salt
12:08 stooj joined #salt
12:22 iceyao_ joined #salt
12:32 cyborg-one joined #salt
12:35 squishypebble joined #salt
12:40 toastedpenguin joined #salt
12:44 toastedpenguin joined #salt
12:53 mvensky joined #salt
12:58 rem5 joined #salt
13:05 sjorge joined #salt
13:07 DammitJim joined #salt
13:11 gomerus[m] thats a very generic question. what do you exactly want to build
13:14 hoonetorg joined #salt
13:16 DammitJim do you guys manage log4j.xml files through salt or continuous integration?
13:18 amcorreia joined #salt
13:22 jas02 joined #salt
13:22 racooper joined #salt
13:26 James5mith joined #salt
13:30 candyman88 joined #salt
13:32 concerti joined #salt
13:33 scoates joined #salt
13:35 candyman88 joined #salt
13:37 mvensky joined #salt
13:38 mavhq joined #salt
13:44 Xenophon1 joined #salt
13:47 candyman89 joined #salt
13:52 jdipierro joined #salt
14:05 PatrolDoom joined #salt
14:06 edrocks joined #salt
14:08 Tanta joined #salt
14:09 antpa joined #salt
14:22 monjwf_ joined #salt
14:27 monjwf joined #salt
14:32 James5mith Question for the channel, any idea on when the repo will be updated to 2016.11-4 ?
14:34 erhandsome joined #salt
14:35 jvelasquez joined #salt
14:38 mavhq joined #salt
14:41 jas02 joined #salt
14:43 ProT-0-TypE is there a function/module to get the time in epoch?
14:45 Xenophon1 James5mith: has 2016.11.4 been released?
14:46 James5mith It shows as the latest stable release.  I thought it had?  https://docs.saltstack.com/en/latest/topics/releases/2016.11.4.html
14:46 James5mith About 9 days ago?
14:47 XenophonF sorry the question was rhetorical - 2016.11.4 has not been released yet
14:47 XenophonF everything shows 2016.11.3 as the current stable release
14:48 DEger joined #salt
14:49 Pyro_ joined #salt
14:51 Pyro_ I have a base, and development environment.  If I put custom _grains in development they don't work, but if I put them in base they do.  Any ideas?  Maybe something in the /etc/salt/master that I'm missing?
14:54 edrocks joined #salt
15:01 Praematura joined #salt
15:02 theblazehen joined #salt
15:03 heaje joined #salt
15:04 jespada joined #salt
15:06 oeuftete joined #salt
15:07 DEger joined #salt
15:08 oeuftete Too busy to open a bug report, but the new version of tornado, 4.5.0, seems to break some file.managed cases in some versions.  This PR: https://github.com/tornadoweb/tornado/pull/1899 (args can no longer be None)
15:08 saltstackbot [#1899][MERGED] Rewrite url_concat function using PythonStandardLibrary | If there is a fragment in the original url, there will be some problem with url_concat function.   ...
15:09 oeuftete Still running 2015.8.10 here, maybe the tornado dep is pinned more tightly in the future, or args is never passed as None from salt.utils.http
15:10 st8less joined #salt
15:13 XenophonF Pyro_: how are you targeting minions in the development environment?
15:14 Pyro_ For the custom grain I assume _grains gets applied to all... (this is where there is probably a lack of understanding), do I need to target grains, like I do salt states, in my top files?
15:16 sarcasticadmin joined #salt
15:18 tapoxi joined #salt
15:19 Pyro_ I just added "match: grain_pcre" to my development matching for 'os:(RedHat|CentOS)':, and that seamed to fix it.  I'll have to read up on grain_pcre, unless you can explain how that works.
15:19 Pyro_ Does grain_pcre trigger the execution of _grains?
15:29 edrocks joined #salt
15:29 PatrolDoom joined #salt
15:30 whytewolf Pyro_: no, running multiple highstates would run the sync process though. first one would sync, second one would update. third might get the result you want.
15:30 whytewolf or you could sync the first time
15:30 sp0097 joined #salt
15:31 whytewolf https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.saltutil.html#salt.modules.saltutil.sync_grains
15:34 ssplatt joined #salt
15:36 Pyro_ Thanks, that gives me some more context.  I'll do some reading from the link above as well, I've taken grains for granted, up to now, and need to dig in and learn more of the details of it at this point.
15:36 whytewolf Pyro_: nothing is actually run out of the _<directory>, they must be synced to the minion using sync modules. and highstate does this at the end of it's run. from the base enviroment if you don't have enviroment set in your minion.
15:37 leonkatz joined #salt
15:37 whytewolf I tend to think of _<directory> as a deployment step. not a run step
15:37 Pyro_ Yeah, thats what I was seeing, I could see the script pulled to the minion, and when I ran it, it returned the grains properly, but something was never syncing them to the master to use when highstate was ran.
15:38 Pyro_ So I think (correct me if I'm wrong, that "grain_pcre" in this case being the first call to sync the grains was what triggered the grains to run?
15:39 whytewolf nope, that was just coincidence
15:41 dezertol joined #salt
15:41 whytewolf grain_pcre is nothing more then hey use this method to search the grains instead of this other method
15:41 Pyro_ OH, I see what I did now....
15:41 londo joined #salt
15:45 Pyro_ I had in the top file "deployment:" then had the ec2 custom grain, which I fixed the file_root to look at the proper location for deploying _grains for that environment, and everything after that was matched off the ec2 tag grain that then existed.
15:47 XenophonF might be simplest to force your minions to sync from the proper environment
15:47 XenophonF something like salt * saltutil.sync_all saltenv=development
15:48 Pyro_ Yeah, I think that may not be a bad idea.
15:48 tiwula joined #salt
15:51 Pyro_ Thanks, as always you all are very helpful!  We are a small shop, and learning this as we go, so we don't have as much buildout context to go by sometimes.  Which results in lots of refactoring ;)
15:53 jas02 joined #salt
15:54 londo joined #salt
15:54 juntalis joined #salt
15:56 mikecmpbll joined #salt
16:08 whytewolf small? I'm a guy that does this by himself for his home projects ;) [my job doesn't use salt, much to my disapointment. and i have tried introducing it]
16:08 XenophonF yay for home projects!
16:09 jas02 joined #salt
16:16 woodtablet joined #salt
16:19 _JZ_ joined #salt
16:20 DEger joined #salt
16:29 icebal joined #salt
16:34 edrocks joined #salt
16:39 leonkatz joined #salt
16:42 sarcasticadmin joined #salt
16:44 Praematura joined #salt
16:50 Pyro_ haha, thats awesume whytewolf.  Hopefully you can get traction at your work.  I've used Puppet, Chef, and CFEngine heavily, and Salt is much better.  Still pretty rough around some of the edges, but it should outrun the others given more time.
16:54 Praematura joined #salt
16:56 whytewolf i have pretty much given up getting work to run salt. large corperation with nails deep into the puppet life. would take more work/money to switch to salt then anyone wants to invest.
16:59 whytewolf so, instead i work on salt from home. and help out in here. and keep my eyes open for a shop running salt that might hire me. hopefully at the level i am currently at at present work. with the work from home i get. ... i'm not holding my breath though
17:00 whytewolf once i get some of my bills payed i might consider a dip in pay. but the place would have to be mind numbingly good for that
17:03 SaucyElf joined #salt
17:16 jas02 joined #salt
17:18 leonkatz joined #salt
17:20 whytewolf you know what would be a useful feature ... being able to color code output the output beyond pass,change,fail
17:22 st8less joined #salt
17:24 cscf whytewolf, based on what criteria?
17:25 whytewolf cscf: mostly for things like a lint that could color code syntax issues
17:25 cscf whytewolf, yeah, distinguishing syntax errors from run errors could be nice.
17:26 st8less joined #salt
17:27 keltim joined #salt
17:37 theblazehen joined #salt
17:44 speedlight joined #salt
17:48 cscf Does anyone have a good workflow/procedure for keeping servers up to date without risking too much breakage?
17:51 v0rtex joined #salt
17:53 Eugene Years of finely-tuned Ops experience ;-)
17:54 Eugene The "standard kit" I use is 1) set up a non-automated rsync mirror of CentOS/EPEL/etc package repos, 2) make yum use the mirror; 3) rsync & test in B environment(or Dev or whatever you call it) before repeating in A
17:59 Rkp joined #salt
17:59 PatrolDoom joined #salt
18:07 whytewolf I perfer the dev/test/stanging/prod method but yeah. pretty much exactly like Eugene. basicly the long and the short of it is, think before act. if it can break it will. and don't rely on anyone you can not hit in the back of the head personally.
18:08 Eugene I label my environments A/B/C because I like to play fast & dirty with prod upgrades.
18:08 Eugene Remove a set of backends from rotation at 2AM, upgrade them, then reverse & finish.
18:09 whytewolf nothing wrong with that. personally i don't like devs touching anything that is considered production. but that is after wars with devs that knew nothing about ops and didn't want to support it after they broke it
18:09 irated Pipelines + Linter + Staging Branch + Production Branch
18:11 whytewolf if you have devs that support it after release. or you are the entire stack from dev to release. nothing wrong with a/b/c
18:12 greyeax joined #salt
18:13 Eugene You can do things like "C normally doesn't go live unless A/B are overloaded; devs only get access to C"
18:13 ajolo left #salt
18:13 Eugene (this actually worked great for me.... up until the overload hapened and C wasn't actually ready.... oh well)
18:13 irated unit tests
18:13 irated I wish salt had a TDD approach like chef
18:14 Eugene Playbooks & checklists are a great technique for sanity, but it takes time(screwups & post-mortems) to build them
18:14 Eugene And you always have the human element of not following them during an emergency
18:20 whytewolf irated: TDD is all well and good. until it isn't. although i agree they shouldn't let something in that doesn't have a test associated with it. but tests by themselves to not in anyway gerentee that things work 100% of the time. many times people are very short sighted in writting their tests.
18:23 overyander joined #salt
18:24 prg3 joined #salt
18:27 jas02 joined #salt
18:31 jdipierro joined #salt
18:38 sysadmin75 joined #salt
18:41 sysadmin75 Hi all, I'm seeing an issue where stopping a minion daemon doesn't kill the main process.
18:42 sysadmin75 salt-minion-2016.11.3-1.el6.noarch
18:42 mswart left #salt
18:43 XenophonF sysadmin75: we'll need more detail than that
18:44 XenophonF presumably a RHEL flavor from the version above, but which precisely?  anything in the logs?
18:44 sysadmin75 https://pastebin.com/ZdtvexEW
18:44 XenophonF does strace or lsof show anything interesting?
18:44 sysadmin75 centos6
18:44 Edgan joined #salt
18:45 XenophonF how long between stopping the server and checking the process listing?
18:45 gtmanfred sysadmin75:that is fixed in 2016.11.4
18:45 gtmanfred which we have tagged
18:45 gtmanfred but isn't out yet
18:45 sysadmin75 ok, that's good to know. Thank you
18:46 gtmanfred lemme see if I can find the pr for you
18:49 XenophonF ah
18:49 XenophonF thanks gtmanfred
18:49 gtmanfred sysadmin75: https://github.com/saltstack/salt/pull/40041
18:49 saltstackbot [#40041][MERGED] Fix transposed lines in salt.utils.process | Resolves #40011.
18:49 gtmanfred there is the fix
18:50 sysadmin75 ty
18:50 gtmanfred no problem
18:50 antpa joined #salt
18:51 aneeshusa joined #salt
18:53 wendall911 joined #salt
18:57 Praematura joined #salt
18:57 aldevar joined #salt
19:03 ry joined #salt
19:04 swills joined #salt
19:04 xMopxShell joined #salt
19:04 st8less joined #salt
19:11 DammitJim joined #salt
19:16 Trauma joined #salt
19:20 domel joined #salt
19:20 keltim joined #salt
19:22 DammitJim how do you guys manage privileges on a salt master?
19:22 DammitJim I would like to give access to the salt master to set up some states, pillar and apply only to test servers
19:22 domel greetings... does anyone know how to pass pillar dictionary keys to orchestration state?
19:22 DammitJim or is that just not possible?
19:24 domel https://gist.github.com/anonymous/c7294245aa389fd7457e0660af19525a
19:25 domel i think you need enterprise version
19:27 domel or you may be able to use api https://docs.saltstack.com/en/latest/ref/netapi/all/salt.netapi.rest_cherrypy.html
19:30 domel and https://docs.saltstack.com/en/latest/topics/eauth/index.html#acl-eauth
19:31 Ryan_Lane what can we do to get upstream to stop accepting boto_* modules that do import of utils, rather than using __utils__?
19:32 Ryan_Lane it's a pretty common thing we need to fix in modules and it's a bit annoying
19:32 Ryan_Lane it would really be ideal for every .utils include to be switched to __utils__
19:36 keltim joined #salt
19:39 gtmanfred Ryan_Lane: add a pylint plugin to the saltpylint?
19:39 Ryan_Lane hm. not sure how difficult that is :)
19:39 gtmanfred not very afaik
19:40 gtmanfred just have to check for salt.utils.boto in any module
19:41 gtmanfred Ryan_Lane: you can probably actually just check the BLACKLISTED_IMPORTS stuff that s0undt3ch added the other day
19:41 gtmanfred https://github.com/saltstack/salt-pylint/commit/57c924ef12fb6323c7e20182bd12ffbb2d371d45
19:42 gtmanfred DammitJim: check out publisher_acls for applying states and limiting their usage by regular users
19:43 gtmanfred if you use eauth, you can limit which minions they are allowed to do anything against
19:52 ahrs joined #salt
19:57 Ryan_Lane @gtmanfred cool. thanks
19:58 gtmanfred :+1:
20:00 paant joined #salt
20:02 jas02 joined #salt
20:06 antpa joined #salt
20:11 XenophonF DammitJim: It might be easier to write a script that performs some canned actions, which users may invoke via sudo.
20:11 ssplatt “[WARNING ] /usr/lib/python2.7/dist-packages/salt/beacons/__init__.py:56: DeprecationWarning: Beacon configuration should be a list instead of a dictionary.”   anyone have an example of what this means? because the docs don’t really show anything.
20:12 ssplatt https://github.com/saltstack/salt/blob/develop/salt/beacons/__init__.py#L51  so it wants a list to convert it to a dict?
20:13 Tanta joined #salt
20:13 keltim joined #salt
20:14 gtmanfred ssplatt: convert all beacon configurations to lists
20:14 gtmanfred so
20:14 gtmanfred beacon:
20:14 gtmanfred thing:
20:14 gtmanfred whatever: thing
20:14 gtmanfred should be
20:14 gtmanfred beacon
20:14 gtmanfred thing:
20:14 gtmanfred - whatever: thing
20:14 antpa joined #salt
20:14 ssplatt ok.
20:14 ssplatt thanks.
20:17 ssplatt hmm that didn’t seem to work
20:18 gtmanfred can you put your beacon configuration into a gist?
20:18 ssplatt https://gist.github.com/ssplatt/03bc237340db13a08cb59306cd4a6a38  is what i just tried and now it’s complaing about network_settings
20:19 ssplatt maybe my indent is off below it
20:20 edrocks joined #salt
20:20 ssplatt should it be -inotify,   and -network_settings?
20:21 ssplatt instead of below that?
20:22 gtmanfred you might try
20:22 gtmanfred beacon:
20:22 gtmanfred - thing
20:22 gtmanfred that might be where the - needs to be
20:23 gtmanfred i forget, it was somewhere they made it so it needed to be changed to a list
20:23 gtmanfred yeah i think that might be it
20:23 ssplatt so - inotify:   and - network_settings....
20:24 ssplatt hmm nope.
20:24 ssplatt TypeError: list indices must be integers, not dict
20:27 gtmanfred grr
20:27 gtmanfred i do not know then, sorry, can you open an issue on github/
20:31 seanz joined #salt
20:31 whytewolf might need 4 spaces instead of 2 for the sub items under say - /sys/block
20:37 ssplatt i tried doing that too.
20:38 whytewolf humm, would be nice if the person who made the change updated the doc examples
20:38 cyborg-one joined #salt
20:39 ssplatt also, the network settings seems to work fine on eth*, but doesn’t seem to work on bond*. anyone used this on bonds or bridges or vlans before?
20:40 ssplatt with success?
20:40 leonkatz joined #salt
20:40 gtmanfred whytewolf: yeah, unfortunately the doc examples have always been all over the map
20:40 gtmanfred if you look at the individual beacons, i thought that those had been updated
20:40 gtmanfred but doesn't appear to be the case
20:43 scottk_ joined #salt
20:44 scottk_ I created a salt state with pkgrepo.managed, and i deployed the state to my minions, now the gpg key url has changed. How can i update the minions?
20:45 gtmanfred put the new gpg key url in the state and run the state on the minion
20:48 cscf ssplatt, I find the network state to be rather incomplete on debian systems, I generally just file.managed into /etc/network/interfaces.d/.
20:48 gtmanfred cscf: have you checked it out with MTecknology's changes in 2016.11?
20:48 ssplatt cscf: me too, but this is teh beacon i’m talking about
20:48 cscf gtmanfred, probably not
20:50 icebal30 joined #salt
20:52 scottk_ thanks
20:52 tapoxi joined #salt
20:55 leonkatz joined #salt
20:59 Praematura joined #salt
21:01 Pyro_ joined #salt
21:03 Pyro_ joined #salt
21:03 Derailed joined #salt
21:04 MTecknology cscf: could you also check out my changes against develop that haven't been merged, yet?
21:05 jas02 joined #salt
21:05 cscf MTecknology, I would like to help, in theory, but don't know if I'll have the time.  I did start setting up a virtualenv dev environment.
21:05 cscf MTecknology, what's the best way to test?
21:06 cowork205 joined #salt
21:06 debian1121 joined #salt
21:07 cowork205 Hi Dears! I wanted to ask whether any of you have on the top of their heads, they way how one would make the state Result: be always True or just to not render it as "red" even when the state Result: False .. ?
21:07 MTecknology cscf: https://github.com/saltstack/salt/issues/19054
21:07 saltstackbot [#19054][OPEN] Set Default Batch Size | It would be lovely if I could set, in a config file, a batch size that is used when a command will go out to too many minions....
21:09 cscf MTecknology, looks like a nice feature
21:09 cscf I didn't even know about -b
21:10 debian112 joined #salt
21:11 MTecknology I've accidentially caused DDOS against data centers becaues of an oopsie with salt '*' state.highstate
21:11 MTecknology kerplow!
21:12 cscf Fun.  My evil empire isn't that big, yet
21:13 cscf Should a typo-fix be agaist stable or dev?
21:14 debian112 joined #salt
21:16 MTecknology /should/ be against develop
21:16 MTecknology This was a long time ago... I wrote the patch but never found time to test it.
21:18 MTecknology cscf: this is all there was to it (I hope)  https://github.com/saltstack/salt/compare/develop...MTecknology:develop
21:19 MTecknology derailed parting during what I'm typing was pretty good timing..
21:19 MTecknology .. almost great
21:20 cscf Oh, heh, the "deleteed" typo in salt-key is already fixed in develop
21:20 gtmanfred yup
21:20 gtmanfred it should be fixed in 2016.11.4
21:20 cyborg-one joined #salt
21:20 Derailed joined #salt
21:21 cscf I'm following this https://docs.saltstack.com/en/latest/topics/development/hacking.html  , anything it misses?
21:23 Ahlee so. How does salt determine if something's running? saltutil.running currently returning state.highstate is running with pid 1084, but I just rebooted that host, so it's impossible for pid 1084 to be highstate
21:23 Tanta it has a job queue
21:24 Ahlee Right, but the queue doesn't exist through reboots
21:27 MTecknology While trying to get gitea packaged for Debian, I ran across an RC bug in a golang package. It's a security problem impacting a crap ton of packages (including things like kubernetes) that now need freeze exceptions to stay in debian. The alternative to this not being fixed is that they get removed from debian entirely. I also have boss man breathing down my back for undefined
21:27 MTecknology projets/goals not being met. Whenevr I get the security thing fixed, I want to get back to packaging gitea which I want done before I rebuild my new git server with debian 9 and that package, and then I want to rebuild the rest of my environment w/ Deb 9 (already have the salt states), and re-deploy my old vm host as part of a new cluster, and then I planned to get back to this salt
21:27 Ahlee gah. /var/cache/salt/minion/proc/
21:27 MTecknology feature, and then start working on a bunch of tools to help me maintain my list of debian packages... then I was thinking about seeing what outside looked like.
21:28 MTecknology I have other projects planned, but those don't really need to ever be completed, just gold plating my home network
21:33 Ahlee the file /var/cache/salt/minion/proc/20170407164537555970 contained a pid for a process that was no longer highstate
21:34 Ahlee minion must have crashed or something else during highstate, and supervisord running salt-minion restarted, causing it to think the process (now a solarflare daemon) was still highstate
21:34 Ahlee shall have to move /var/cache/salt to a tmpfs so it goes away when rebooted to prevent this
21:34 sysadmin75 I'm sorry if this is a noob question, but I'm looking at the config file for the salt master and I don't see anything that shows the interval for the master to apply states to the minions.  What am I missing?
21:35 whytewolf sysadmin75: https://docs.saltstack.com/en/latest/topics/jobs/
21:36 whytewolf the master doesn't auto apply states. you have to set a schedule for minions to run highstate [or states]
21:36 sysadmin75 ok, I'll read that over. Thanks
21:59 cscf I'm running salt-master and minion in a virtualenv, using root_dir option for both.  Yet when I try to file.manage a file in /var, it tries to write to actual /var and can't.
22:02 cscf Ah, I think I fixed it.  Accidentally had some paths specified in real paths, where they should have been relative.  Should fail in a better way than that, though...
22:07 Pyro_ joined #salt
22:31 justanotheruser joined #salt
22:40 secrgb joined #salt
22:53 teratoma joined #salt
22:58 SaucyElf joined #salt
23:01 Praematura joined #salt
23:04 edrocks joined #salt
23:13 jas02 joined #salt
23:38 Rkp joined #salt
23:48 st8less joined #salt
23:50 leonkatz joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary