| *** tmickelson has quit (Ping timeout: 480 seconds) | 00:02 | |
| *** shmohamud has quit (Remote host closed the connection) | 00:53 | |
| *** shmohamud has quit (Remote host closed the connection) | 00:56 | |
| *** tmickelson has quit (Quit: leaving) | 01:05 | |
| *** shmohamud has quit (Remote host closed the connection) | 01:20 | |
| *** shmohamud has quit (Remote host closed the connection) | 02:22 | |
| scooper | Good morning Jeff | 10:12 |
|---|---|---|
| scooper | I saw your email yesterday that you addressed to the supe..... | 10:12 |
| scooper | secondly Freena will not be the today | 10:13 |
| tboimah | Good morning Jeff | 10:49 |
| jelkner | where in the wrong channel | 11:00 |
| jelkner | let's meet over in accict | 11:00 |
| *** scooper has quit (Ping timeout: 480 seconds) | 11:00 | |
| *** jelkner has quit (Quit: Leaving) | 11:10 | |
| *** dcammue has quit (Quit: Leaving) | 11:11 | |
| shmohamud | Hi Tboimah and Sysadmin | 11:46 |
| tboimah | Good morning shmohamud | 11:46 |
| shmohamud | what are you learning these days? | 11:46 |
| tboimah | linux sysadmin | 11:47 |
| shmohamud | cool cool. Do you have any questions for me? | 11:47 |
| tboimah | no not now but i will email you if i have any. | 11:48 |
| tboimah | thanks anyway | 11:48 |
| shmohamud | ok | 11:51 |
| shmohamud | sounds good | 11:51 |
| *** shmohamud has quit (Remote host closed the connection) | 12:02 | |
| *** shmohamud has quit (Remote host closed the connection) | 12:06 | |
| scooper | Hello Shmohamud | 12:27 |
| mulbah | Hello Mr. Cole | 13:04 |
| ubuntourist | Hi tboimah hope you're feeling better | 13:04 |
| ubuntourist | Hi mulbah | 13:04 |
| tboimah | Good morning Mr Cole | 13:04 |
| tboimah | Yeah Much better them the past days | 13:04 |
| ubuntourist | tboimah, I've just learned that my Irish Flute teacher has come down with COVID. I'm hoping to get the latest vaccine soon, but it will not be available until roughly two weeks from now. | 13:06 |
| tboimah | Ahhh okay | 13:06 |
| mulbah | But we can email you right | 13:06 |
| ubuntourist | tboimah, Monday mulbah and I detoured a bit. | 13:07 |
| tboimah | Yeah i read the log, you too was talking about regex and it sister wildcard | 13:07 |
| ubuntourist | mulbah, I'm not sick. I'm hoping to avoid getting sick. So I am hoping that the newest vaccine will be available soon. | 13:08 |
| ubuntourist | tboimah, ok. if you're feeling "caught up" and don't have questions, I'll continue from the end of Monday's log. | 13:09 |
| tboimah | yeah you can. | 13:09 |
| ubuntourist | I explained to mulbah in e-mail that the reason for Monday's work was that I wanted to find a good example of a system | 13:10 |
| mulbah | okay I pray you shouldn't get sick | 13:10 |
| ubuntourist | configuration file that was very large, and filled with comments. | 13:10 |
| ubuntourist | There is an English expression which you may have read or heard: "He cannot see the forest from the trees" | 13:11 |
| ubuntourist | which refers to a situation where there are so many little details that it becomes difficult to recognize the "bigger picture". | 13:12 |
| ubuntourist | By focusing on every individual tree as a separate, unique object, it can be hard to recognize that the collection of trees are part of a "whole" forest. | 13:14 |
| ubuntourist | So the goal today: | 13:14 |
| ubuntourist | Look at a HUGE file, and realize that maybe, we can make it "simpler" to see what the file is actually doing. | 13:15 |
| ubuntourist | So, I think I want to do things a little backwards today.... Hold for one moment. | 13:15 |
| ubuntourist | Today, I'm running the tmate. I want both of you to join me at | 13:16 |
| ubuntourist | ssh E96DDEHef7V3Dhx4mgZ22Vzy3@lon1.tmate.io | 13:16 |
| mulbah | ssh 3AdYAVvMC23GSDTbPetssFDyQ@lon1.tmate.io | 13:16 |
| mulbah | okay | 13:16 |
| tboimah | okay | 13:17 |
| tboimah | I am connected, can you see me? | 13:18 |
| ubuntourist | I see one extra connection. | 13:18 |
| ubuntourist | OK, looks like you're both here. | 13:18 |
| ubuntourist | So, on the screen now, you can see Monday's "cd /etc" and the egrep ... | grep ... | sort ... | 13:20 |
| ubuntourist | We've learned from this that /etc/lvm/lvm.conf has 1961 lines that start with "#". | 13:22 |
| ubuntourist | So, do either of you remember the command to show how many lines (total) are in a file? (It is a very short command.) | 13:22 |
| mulbah | yeah | 13:23 |
| mulbah | wc -l | 13:24 |
| ubuntourist | mulbah, correct. So, go ahead and see how many lines are in the file we're looking at. | 13:24 |
| mulbah | for example "most /etc/lvm/lvm.conf | wc -l | 13:25 |
| ubuntourist | Not exactly. No. It's even simpler. | 13:25 |
| ubuntourist | wc -l lvm/lvm.conf | 13:26 |
| ubuntourist | (We don't need the /etc because we are already "cd /etc" | 13:26 |
| ubuntourist | Nope. | 13:27 |
| ubuntourist | The 1961 is not part of the file name. | 13:27 |
| ubuntourist | 1961 is the "answer" to "How many lines start with #?" | 13:27 |
| ubuntourist | 1961 lines in the file lvm/lvm.conf start with "#" | 13:28 |
| ubuntourist | And the total number of lines in the file is 2302. | 13:28 |
| ubuntourist | So, out of 2302 lines, 1960 are comments. | 13:28 |
| ubuntourist | That means that only 341 lines (2302 -minus 1961) are actuallyt DOING anything. | 13:30 |
| ubuntourist | Think of your Python programs. If all your lines start with "#" then the "program" does nothing. | 13:30 |
| ubuntourist | So, looking at the file lvm/lvm.conf, we can see that the comments are designed to instruct a systems | 13:31 |
| ubuntourist | administrator about how to use this file. | 13:32 |
| ubuntourist | (Don't worry too much about understanding what this file does. It is a list of settings that are used | 13:32 |
| ubuntourist | to control something called the Logical Volume Management (LVM) system. | 13:33 |
| ubuntourist | The important idea here is that the comments give you an idea of what the file is for, | 13:33 |
| ubuntourist | where to find more information, and how to modify the file. | 13:34 |
| ubuntourist | If you look on the screen now, without scrolling, how many lines are actually doing something? | 13:35 |
| ubuntourist | (How many lines are not comments and not blank?) | 13:35 |
| tboimah | 1 line | 13:35 |
| ubuntourist | Nope. | 13:35 |
| mulbah | two | 13:36 |
| ubuntourist | Nope. | 13:36 |
| tboimah | it is three(3) line | 13:36 |
| ubuntourist | Yes: | 13:36 |
| ubuntourist | config { | 13:36 |
| ubuntourist | checks = 1 | 13:36 |
| ubuntourist | abort_on_errors = 0 | 13:37 |
| ubuntourist | Above the "checs = 1" is a description of what the "checks" option setting does. | 13:37 |
| ubuntourist | Above "abourt_on_errors", again, there is a short explanation of its purpose. | 13:38 |
| ubuntourist | The entire file is like that: Lots of descriptions of purpose, followed by actual lines that do someting. | 13:38 |
| jelkner | !add Discuss SECOSOL website deployment | 13:39 |
| LittleWebster | Success: "Discuss SECOSOL website deployment" has been added to the agenda. | 13:39 |
| jelkner | !agenda | 13:39 |
| LittleWebster | This is the agenda for the next meeting: | 13:39 |
| LittleWebster | Discuss SECOSOL website deployment (added by jelkner) | 13:39 |
| ubuntourist | But that's 2302 lines! It's a LOT to look at. | 13:39 |
| ubuntourist | So, we're going to cut it down to size and see only the lines that are NOT comments. | 13:40 |
| ubuntourist | (We're also going to eliminate the blank lines from being shown.) | 13:40 |
| ubuntourist | We're going to use my favorite toy, grep. | 13:41 |
| ubuntourist | Really, we're going to use the fancier "egrep". | 13:41 |
| ubuntourist | So. we know: | 13:42 |
| ubuntourist | "^" means "at the beginning of a line" | 13:43 |
| mulbah | sure | 13:43 |
| ubuntourist | "[[:space:]]*" meas zero or more spaces or tabs (characters that leave empty space) | 13:44 |
| ubuntourist | "#" is not a special character. So it just means "#" | 13:44 |
| ubuntourist | ".*" means zero or more of... anything. Any character. | 13:45 |
| ubuntourist | And finally "$" means "at the end of a line" | 13:45 |
| ubuntourist | We've also talked about "?" and "+". "?" means zero or one and "+" means one or more. | 13:47 |
| ubuntourist | OK. Think about what you just tried in the command line. Each section between pipes must be a complete command. | 13:48 |
| ubuntourist | Try to explain each part without referring to the other parts, and I think you may see your mistake. | 13:49 |
| mulbah | who? | 13:50 |
| ubuntourist | Whoever typed in the terminal. (I cannot tell which one of you is typing. | 13:50 |
| mulbah | it's tboimah | 13:50 |
| ubuntourist | Or, whichever one of you wants to try explaining. | 13:50 |
| mulbah | but I can correct it | 13:51 |
| ubuntourist | tboimah, stop for a minute. mulbah go ahead. | 13:51 |
| tboimah | okay | 13:52 |
| ubuntourist | So. Stop mulbah | 13:52 |
| ubuntourist | Again, each part of between the pipes must make sense by itself. | 13:53 |
| ubuntourist | Think about "wc -l" alone, and then egrep egrep "^[[:space:]]*#" alone and finally "lvm/lvm.conf" alone. These do not make sense. | 13:55 |
| ubuntourist | The first thing on a command line must make sense all by itself. And if you are using a pipe, then | 13:55 |
| ubuntourist | that first command must produce output, and the second command after the pipe must accept the output from | 13:56 |
| ubuntourist | the first command, as input. Then the next pipe is the same: It must accept output from the second | 13:56 |
| ubuntourist | command and use it as input to the third command. | 13:57 |
| ubuntourist | And you can keep going like that: First command feeds second command feeds third command feeds fourth command, etc. | 13:57 |
| ubuntourist | So "wc -l" is not a complete command. and "lvm/lvm.conf" is not a command at all -- it is just a file name. | 13:58 |
| ubuntourist | I think maybe I need to slow down... | 13:59 |
| ubuntourist | The bash error is a little misleading here: It is telling you that you do not have permission to execute "lvm/lvm.conf" | 14:01 |
| tboimah | yeah | 14:01 |
| ubuntourist | as a command. Well, that's for two reasons: First, you are trying to run something in a system-controlled directory and you are not the SuperUser administrator. | 14:02 |
| ubuntourist | But more important: It's NOT a command, and even with "sudo" it would not run. | 14:02 |
| ubuntourist | It is a file but it is not a program. It is a file that contains a list of settings and options. It is not an application. | 14:03 |
| ubuntourist | Agan: each part of a pipe must contain an executable command (a program, application, script, or built-in command) | 14:05 |
| ubuntourist | Let me go back to what we're trying to do: | 14:05 |
| tboimah | i think now i got it | 14:06 |
| ubuntourist | "wc -l" doesn't show lines. It shows counts. And we're getting VERY close to the right answer. | 14:07 |
| ubuntourist | Stop. | 14:07 |
| ubuntourist | Analysze the commands that responded 1961 | 14:08 |
| ubuntourist | Stop a minute. | 14:08 |
| *** mulbah has quit (Ping timeout: 480 seconds) | 14:09 | |
| ubuntourist | Before you continue, explain the line that gave 1961 as a result. | 14:09 |
| ubuntourist | (And I will say that the line with the "most" is even closer to correct, but before continuing, I want one of you to | 14:11 |
| ubuntourist | explain the line before that one. The one that gave 1961 as a result.) | 14:11 |
| tboimah | The command is saying that eliminate the blank lines from being shown and also eliminate the comment "#" in the file lvm/lvm.conf | 14:12 |
| ubuntourist | Nope. | 14:13 |
| ubuntourist | First: Explain what "egrep" is for. Forget about the rest of tle line. forget about "^[[:space:]]*#" lvm/lvm.conf | wc -l | 14:14 |
| ubuntourist | Then explain "^[[:space:]]*#" | 14:15 |
| ubuntourist | Then explain "wc -l" | 14:15 |
| ubuntourist | Three separate explanations. Don't try to put them together yet. | 14:15 |
| tboimah | egrep is a tool that searches for patterns in a specified location | 14:17 |
| ubuntourist | (Or I can try again to break it up and explain it in pieces. And then you can try to put the pieces together.) | 14:17 |
| ubuntourist | ACTION waits for an opinion on how to continue... | 14:18 |
| tboimah | okay you can go ahead and explain better | 14:19 |
| ubuntourist | tboimah, Excellent start. (I missed your response at first.) | 14:19 |
| ubuntourist | So, yes! The first part. exactly right: egrep a tool that searches for patterns in a specified location | 14:20 |
| tboimah | and ^ in the command mean at the begging | 14:21 |
| ubuntourist | grep and egrep search files for patterns --- OR they search the output of another command for patterns | 14:21 |
| tboimah | "^[[:space:]]" so the command is saying that at the begging of the line the leave empty space | 14:22 |
| ubuntourist | So, when you use grep or egrep, you need the command ("grep" or "egrep"), you need a regular expression (regex) pattern, | 14:22 |
| ubuntourist | and you need EITHER a file name at the end OR a pipe at the beginning. The pipe will "feed" the command in the same way as a file would. | 14:23 |
| ubuntourist | grep and egrep want data from somewhere. If the command before the pipe produces output, then grep or egrep will | 14:24 |
| ubuntourist | read that and use it as the data to search. If there is no pipe, there must be a file for grep or egrep to read and use as data. | 14:24 |
| ubuntourist | And the second part "^[[:space:]]*#" is not a command. It is a regular expression (regex) pattern that grep or egrep uses. | 14:26 |
| ubuntourist | There are MANY other commands, applications, programs, scripts and tools that use regular expression patterns. | 14:27 |
| ubuntourist | With a little bit of work you can make Python programs work with regular expression patterns. | 14:27 |
| ubuntourist | So, it's important not to say things like "^ in the command". (Technically, in this case, yes, it's 'part' of | 14:29 |
| tboimah | okay should i go ahead and explain | 14:31 |
| ubuntourist | the "egrep" comman line, but it's not part of the command. When you type "nano thomas.txt", thomas.txt isn't 'part' of the "nano" command.) | 14:31 |
| ubuntourist | ok... | 14:31 |
| ubuntourist | go ahead. | 14:31 |
| tboimah | "^[[:space:]]*#" this is saying that at the begging of a line that have empty space and a comment | 14:32 |
| tboimah | and the wc -l is a command that say count the amount of line and print them | 14:32 |
| tboimah | ACTION done | 14:34 |
| jelkner | !add Who should represent us at USFWC annual meeting https://info.usworker.coop/civicrm/event/info ? | 14:34 |
| LittleWebster | Success: "Who should represent us at USFWC annual meeting https://info.usworker.coop/civicrm/event/info ?" has been added to the agenda. | 14:34 |
| jelkner | !agenda | 14:34 |
| LittleWebster | This is the agenda for the next meeting: | 14:34 |
| LittleWebster | Discuss SECOSOL website deployment (added by jelkner) | 14:34 |
| LittleWebster | Who should represent us at USFWC annual meeting https://info.usworker.coop/civicrm/event/info ? (added by jelkner) | 14:34 |
| ubuntourist | Not bad. But in the computer business (and a lot of other science) precision is everything. So, for number two: | 14:35 |
| ubuntourist | ^[[:space:]]*#" is saying at the beginning of a line, ZERO or more empty space followd by a comment character. | 14:37 |
| ubuntourist | In other words, we will accept: | 14:37 |
| ubuntourist | # | 14:37 |
| ubuntourist | # | 14:37 |
| ubuntourist | # | 14:37 |
| ubuntourist | but wie will NOT accept | 14:38 |
| ubuntourist | x = 4 # | 14:38 |
| ubuntourist | most thomas.txt # | 14:38 |
| ubuntourist | ls -l # | 14:38 |
| tboimah | Ahh okay | 14:39 |
| mulbah | My internet connection trape | 14:39 |
| mulbah | so I did connect | 14:40 |
| ubuntourist | Our pattern says starting at the beginning of the line "^" the ONLY acceptable matches are zero or more spaces "[[:space:]]*" followed by "#". | 14:40 |
| mulbah | so I disconnect | 14:40 |
| ubuntourist | mulbah, I guessed that was the problem. | 14:40 |
| ubuntourist | So, now tboimah you've explained the pieces pretty well. Using your three explanations,and understanding what the pipes "|" are for, explain the whole command | 14:42 |
| ubuntourist | egrep "^[[:space:]]*#" lvm/lvm.conf | wc -l | 14:42 |
| tboimah | ollay | 14:42 |
| tboimah | okay | 14:43 |
| ubuntourist | What did the first command produce as output for the second command? | 14:43 |
| tboimah | the comman is saying that eliminate any line in the file lvm/lvm.conf that have empty space at the beginning and a comment and print out the amount of line | 14:47 |
| mulbah | no tboimah | 14:48 |
| ubuntourist | Nope. Where do you see any indication that the match is eliminated? | 14:48 |
| mulbah | that isn't what the command is saying | 14:48 |
| ubuntourist | mulbah, | 14:48 |
| ubuntourist | mulbah, go ahead | 14:48 |
| tboimah | the command is saying that search any line in the file lvm/lvm.conf that have empty space at the beginning and a comment and print out the amount of line | 14:49 |
| ubuntourist | I wish we had a real, live classroom. ;-) it is hard when both of you are trying to respond, and whoever types the fastest, wins. ;-) | 14:50 |
| ubuntourist | But yes, tboimah, correct. | 14:51 |
| mulbah | okay | 14:51 |
| ubuntourist | So, NOW we actually WANT to eliminate the match. Easy, if you remember which option does that. | 14:52 |
| tboimah | yeah i was not thinking that their is -v in the command | 14:52 |
| ubuntourist | And, we don't want to see the number of lines. We want to see the lines. | 14:52 |
| tboimah | no* | 14:52 |
| ubuntourist | tboimah, right again. | 14:52 |
| ubuntourist | (But we don't want to see the count. We want to see the contents.) | 14:53 |
| ubuntourist | Go ahead in the terminal window. | 14:53 |
| tboimah | you can only eliminate when you are using -v with the grep or egrep command | 14:53 |
| ubuntourist | Just edit the previous command and add in your fix | 14:54 |
| ubuntourist | You didn't make the little change to the line to eliminate matches.... | 14:55 |
| ubuntourist | I see you've been practicing some of the keyboard shortcuts. Excellent. | 14:56 |
| ubuntourist | BINGO! | 14:56 |
| tboimah | now it works | 14:56 |
| *** scooper has quit (Ping timeout: 480 seconds) | 14:57 | |
| ubuntourist | We haven't eliminated the blank lines yet but NOW you are ONLY seeing lines that actually DO work. | 14:57 |
| ubuntourist | As a systems administrator, you will be faced with problems like "Why is LVM not creating a log file showing me | 14:58 |
| ubuntourist | its activity? I searched for the log file, but could not find it!' | 14:58 |
| ubuntourist | When you meet a problem like that, your first thought should be: | 14:59 |
| ubuntourist | "Something is probably wrong with a configuration file somewhere. | 14:59 |
| ubuntourist | Since I am looing for the LVM log file, the configuration for LVM is PROBABLY somewhere in the /etc directories | 15:00 |
| ubuntourist | and PROBABLY has a name that ends with ".conf" or ".config". A good guess would be "lvm.conf"... | 15:00 |
| ubuntourist | locate lvm.conf | 15:00 |
| ubuntourist | Oh, look: There it is /etc/lvm/lvm.conf! | 15:01 |
| ubuntourist | Okay, I found it, but it's HUGE! | 15:01 |
| ubuntourist | Let me see the file without comments. | 15:01 |
| *** shmohamud has quit (Remote host closed the connection) | 15:02 | |
| ubuntourist | Oh look: I see that the "syslog" option is set to equal 0, and I suspect that 0 means "false" or "off" or "disabled" | 15:02 |
| ubuntourist | That's probably why I am not able to find the log: Logging has been disabled! | 15:03 |
| ubuntourist | Now let's look at the whole file with comments to see if my guess is correct.... | 15:03 |
| ubuntourist | ... | 15:03 |
| ubuntourist | That'ss the kind of diagnostic thinking that you will be getting a lot of practice with. | 15:03 |
| tboimah | okay | 15:04 |
| mulbah | Okay Mr. Cole | 15:04 |
| ubuntourist | Some files do not use "#" as a comment. For example configuration files that use C++ commenting use "//" to mean "comment" | 15:05 |
| ubuntourist | Others use ";" instead of "#". | 15:05 |
| ubuntourist | Because I do this type of thinking about probems ALL THE TIME, I have created an alias to make my life simpler. | 15:06 |
| ubuntourist | alias decomment='egrep -v "^[[:space:]]*((#|;|//).*)?$" ' | 15:06 |
| ubuntourist | Now i can "de-comment" with the decomment alias: | 15:07 |
| ubuntourist | decomment lvm/lvm.conf | most | 15:07 |
| ubuntourist | (And my pattern eliminates the blank lines too.) | 15:07 |
| tboimah | wow! cool | 15:08 |
| ubuntourist | We can see on the screen now that there is a section called "log" | 15:08 |
| tboimah | +1 | 15:08 |
| ubuntourist | with settings like verbosse, silent, syslog, etc. and they are mostly 0 and 1. So, disabled and enabled. | 15:09 |
| ubuntourist | If you were wanting the logs to be much larger and more descriptive, you would edit /etc/lvm/lvm.conf, and change "verbose = 0" to "verbose = 1" | 15:10 |
| ubuntourist | enabling it. | 15:10 |
| ubuntourist | But before finish today, now that I *think* I know how to enable more logging, I can NOW look at the commented version | 15:11 |
| ubuntourist | with "most" and search for the word "verbose". | 15:11 |
| ubuntourist | Nope, that's talking about "checks". "n" to search again... | 15:12 |
| ubuntourist | There it is: Conviguration option log / verbose: Controls the messages sent to stdout or stderr. | 15:13 |
| ubuntourist | (It's not a great explanation, but it's something. We can see that "silent = 0" has a much longer explanation.) | 15:14 |
| ubuntourist | I'm very proud of my decomment alias, and have shared it with a lot of systems administrators, | 15:15 |
| ubuntourist | because it makes the job so much easier.. | 15:15 |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 15:15 | |
| tboimah | sure | 15:15 |
| ubuntourist | And you can try it on Python code, or anything else that uses "#", ";" or "//" for comments. | 15:15 |
| ubuntourist | Monday, we'll put the "decomment" alias into our .bash_aliases file to make it "permanent". | 15:16 |
| mulbah | Alright | 15:17 |
| ubuntourist | We looked at a 2302-line file and found out that there are only 96 lines in the file that are actively doing something useful. | 15:18 |
| ubuntourist | much easier to look at 96 lines to find out where the trouble is, and THEN search the 2302 lines for that trouble spot. | 15:19 |
| ubuntourist | (That's why we did the work Monday -- I wanted to find a big example with lots and lots of comments.) | 15:20 |
| ubuntourist | You can see on the list now that there are several files with lots of comments, like /etc/postgresql/13/main/postgresql.conf | 15:24 |
| ubuntourist | with 623 comment lines. | 15:25 |
| ubuntourist | You can use the same techniques to see which lines are active... | 15:25 |
| ubuntourist | Anyway, that's all for today! | 15:25 |
| mulbah | Alright Thanks for today Mr. Cole | 15:26 |
| tboimah | Okay thanks for today | 15:26 |
| tboimah | we really appreciate | 15:26 |
| mulbah | and we promise to practice with the other file | 15:27 |
| mulbah | using the same techniques | 15:27 |
| ubuntourist | I appreciate the effort you are putting into this. There is a lot to learn, and a lot to remember. So keep good notes for yourselves. | 15:27 |
| *** ubuntourist has quit (Quit: Leaving) | 15:27 | |
| *** tboimah has quit (Quit: Leaving) | 15:28 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 15:37 | |
| *** shmohamud has quit (Remote host closed the connection) | 15:42 | |
| *** mulbah has quit (Ping timeout: 480 seconds) | 15:43 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 16:03 | |
| *** mulbah has quit (Ping timeout: 480 seconds) | 16:12 | |
| *** sysadmin_ has quit (Quit: Leaving) | 16:42 | |
| *** shmohamud has quit (Remote host closed the connection) | 17:29 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 17:40 | |
| *** mulbah has quit (Ping timeout: 480 seconds) | 18:02 | |
| *** jelkner has quit (Quit: Leaving) | 18:27 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 19:22 | |
| *** shmohamud has quit (Remote host closed the connection) | 20:13 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 21:08 | |
| *** LittleWebster has joined #novawebdev | 21:28 | |
| fkoikoi | !agenda | 21:57 |
| LittleWebster | This is the agenda for the next meeting: | 21:57 |
| LittleWebster | Discuss SECOSOL website deployment (added by jelkner) | 21:57 |
| LittleWebster | Who should represent us at USFWC annual meeting https://info.usworker.coop/civicrm/event/info ? (added by jelkner) | 21:57 |
| fkoikoi | !add AOB | 21:59 |
| LittleWebster | Success: "AOB" has been added to the agenda. | 21:59 |
| *** fkoikoi has quit (Quit: Leaving) | 22:06 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 22:07 | |
| *** tmickelson has quit (Ping timeout: 480 seconds) | 22:39 | |
| *** shmohamud has quit (Ping timeout: 480 seconds) | 22:46 | |
| *** shmohamud has quit (Remote host closed the connection) | 23:37 | |
| *** tmickelson has quit (Ping timeout: 480 seconds) | 23:37 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!