00:15 | Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 252 seconds) | |
00:34 | mmarconm has joined IRC (mmarconm!~mmarconm@179.254.146.18) | |
00:58 | yanu has left IRC (yanu!~yanu@178-116-60-189.access.telenet.be, Ping timeout: 240 seconds) | |
00:58 | yanu has joined IRC (yanu!~yanu@178-116-60-189.access.telenet.be) | |
01:38 | adrianor1 has joined IRC (adrianor1!~adrianorg@186.213.155.204) | |
01:41 | adrianorg has left IRC (adrianorg!~adrianorg@186.215.21.136, Ping timeout: 248 seconds) | |
01:50 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
01:53 | adrianor1 is now known as adrianorg | |
02:51 | mmarconm has left IRC (mmarconm!~mmarconm@179.254.146.18, Quit: Leaving) | |
04:44 | * bennabiy knows nothing about configuring dnsmasq | |
04:44 | <bennabiy> I just used what was included with ltsp-manager
| |
04:48 | <alkisg> bennabiy: want me to vnc and see?
| |
04:48 | It's not only about configuring dnsmasq, it's about configuring ubuntu correctly
| |
04:48 | When you divert from the defaults (network-manager), you're supposed to also configure all the side-effects...
| |
04:49 | <bennabiy> we could do a vnc, I have a few minutes
| |
04:49 | I just got our internet back up
| |
04:49 | <alkisg> OK
| |
04:49 | !vnc-dide
| |
04:49 | <ltsp> vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
| |
04:51 | <alkisg> bennabiy: open a terminal
| |
04:51 | <bennabiy> let me clear some stuff
| |
04:51 | <alkisg> Resize it to be a bit smaller
| |
04:51 | E.g. 1600x1000
| |
04:53 | Do you want to use dnsmasq as a dns server for the clients?
| |
04:53 | It speeds up things...
| |
04:53 | <bennabiy> sure
| |
04:53 | <alkisg> In 192.168.5, are you proxy or real dhcp?
| |
04:54 | <bennabiy> 5 is real dhcp, 0.0 is my main network
| |
04:54 | <alkisg> Do you want clients to boot from the ltsp server in the main network?
| |
04:54 | (proxy)
| |
04:54 | <bennabiy> they could
| |
04:58 | what are your thoughts?
| |
05:00 | did we get booted again?
| |
05:01 | fixed again
| |
05:13 | <alkisg> bennabiy: I'm thinking that network manager overrides your dns servers, because you still have it installed there
| |
05:13 | It's certainly strange behaviour...
| |
05:17 | OK
| |
05:17 | <bennabiy> do you see why I have been hesitant at getting it working?
| |
05:18 | <alkisg> The problem is when you divert from the defaults
| |
05:18 | <bennabiy> which defaults?
| |
05:18 | <alkisg> network manager...
| |
05:18 | <bennabiy> like having a bridge?
| |
05:18 | <alkisg> No, of course not
| |
05:18 | A bridge isn't the problem
| |
05:18 | Leaving nm installed while not using it, is
| |
05:19 | nm configures resolvconf so that nm manages dns servers
| |
05:19 | <bennabiy> I usually remove it on my servers
| |
05:19 | <alkisg> And you have nm configured to not provide any dns servers at all
| |
05:19 | <bennabiy> yes
| |
05:19 | <alkisg> Well, it's best to keep it, it will give you less headaches like this
| |
05:20 | <bennabiy> can I try and boot a client now?
| |
05:20 | <alkisg> Sure
| |
05:20 | <bennabiy> I have not tried since I removed isc-
| |
05:23 | <alkisg> All ok?
| |
05:23 | Btw, how do you know if the network cable is disconnected, when not using network manager?
| |
05:24 | <bennabiy> If my connections stop working...
| |
05:24 | I check my cable
| |
05:25 | <alkisg> That could mean any other number of things :)
| |
05:25 | <bennabiy> yes
| |
05:25 | <alkisg> I don't see any benefit in not using network manager, especially replacing it with ifupdown which is going to be removed
| |
05:25 | Statler has joined IRC (Statler!~Georg@p579FED9E.dip0.t-ipconnect.de) | |
05:25 | <bennabiy> I have been bitten by NM in the past, and do not like it... I use it for my laptop which changes networks often, but for servers and desktops, I do not see a need for it
| |
05:26 | <alkisg> Why not use systemd-networkd then, which is replacing ifupdown?
| |
05:26 | <bennabiy> because I have not learned it yet
| |
05:28 | <alkisg> And now you have been bitten by ifupdown :D
| |
05:28 | <bennabiy> looks like clients boot fine... now wher ewould I put the declaration about if64 etc?
| |
05:28 | no, this was still nm
| |
05:28 | <alkisg> !ifcpu
| |
05:28 | <ltsp> Error: "ifcpu" is not a valid command.
| |
05:28 | <alkisg> No, the problem is that ifupdown doesn't propagate its servers to resolvconf
| |
05:29 | nm properly reads resolvconf, it wasn't the issue there
| |
05:29 | <bennabiy> but nm was even overriding your manually set settings for dnsmasq as well as resolvconf!
| |
05:30 | not ifupdowns fault ;)
| |
05:30 | <alkisg> When resolvconf is installed, dnsmasq ignores resolv-file directives unless you modify /etc/default/dnsmasq
| |
05:30 | I didn't know that, because I never had to tell dnsmasq about upstream dns servers,
| |
05:30 | because resolvconf managed that, by properly working with nm
| |
05:31 | Since resolvconf doesn't properly work with ifupdown, I had to configure dnsmasq to solve the bug in ifupdown
| |
05:31 | <vagrantc> resolvconf *used* to work with ifupdown, but somewhere along the way it got brokenified
| |
05:31 | <bennabiy> yes
| |
05:31 | <alkisg> So the first problem was ifupdown; the second was my lack of knowledge on how to fix the ifupdown bug using dnsmasq
| |
05:31 | <vagrantc> but in any case, i don't think ifupdown will be around much longer
| |
05:32 | <bennabiy> which will then cause me to look at another option
| |
05:32 | <alkisg> For ifcpu, vagrantc has some code in /usr/share/ltsp/update-kernels
| |
05:32 | * bennabiy waves at vagrantc | |
05:33 | <alkisg> You put ifcpu64 in update-kernels.conf or something, and it creates a stanza in the pxelinux file, which you can then use to autoboot x32 or x64
| |
05:33 | <bennabiy> it is funny, I didn't realize you were you until I looked closer at the names
| |
05:33 | well, alkisg thank you for your help
| |
05:33 | <alkisg> np
| |
05:34 | <bennabiy> I still need to dig a trench tonight and get ready for a 5 AM store run for some conduit to properly fix the internet here
| |
05:34 | <vagrantc> it's been a long time since i've tested the ifcpu64 support ...
| |
05:34 | some of ubuntu's kernel naming sort of broke it
| |
05:39 | <bennabiy> I can try it out if you like, but not right now :)
| |
05:39 | good night all!
| |
05:39 | and good morning alkisg
| |
05:39 | * alkisg waves :) | |
05:41 | <vagrantc> night and morning
| |
06:09 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
06:20 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
06:39 | <bcg> bennabiy: NM supports bridges.
| |
06:41 | Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr) | |
07:11 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds) | |
07:12 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
07:13 | Statler has left IRC (Statler!~Georg@p579FED9E.dip0.t-ipconnect.de, Remote host closed the connection) | |
07:43 | Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de) | |
07:52 | zamba has left IRC (zamba!marius@flage.org, Ping timeout: 258 seconds) | |
08:04 | zamba has joined IRC (zamba!marius@flage.org) | |
08:11 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
08:26 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
08:37 | kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:b834:80db:66e2:6ed0) | |
09:17 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Remote host closed the connection) | |
09:18 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
09:24 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
09:43 | markanthonyfelix has joined IRC (markanthonyfelix!775db2f0@gateway/web/freenode/ip.119.93.178.240) | |
10:59 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 248 seconds) | |
11:10 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
12:22 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Remote host closed the connection) | |
12:23 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
12:40 | gchaos has joined IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7) | |
12:41 | gchaos has joined IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7) | |
12:49 | gchaos has left IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7, Ping timeout: 255 seconds) | |
12:49 | gchaos has joined IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7) | |
12:50 | Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 255 seconds) | |
12:59 | <gchaos> Hello everybody, I am doing some research on LTSP (version: 5.5.9-2) running on Debian9.
| |
12:59 | So, after building a new fat client chroot=office-i386-xfce4 arch=i386 and booting the Squashfs file's client located at its default path (/opt/ltsp/images/office-i386-xfce4.img) through nbd-server, everything seems to work. When I generate a new lts.conf file to this client (ltsp-config lts.conf) it generates the file in its right place at /var/lib/tftpboot/ltsp/office-i386-xfce4/lts.conf
| |
13:00 | The problem is, it doesn’t load any config I do in the lts.conf file. I did some tests and I found out, using “tcpdump -i ens3 port 69” that the client is looking fot the lts.conf file at another location, instead of lookig for /var/lib/tftpboot/ltsp/office-i386-xfce4/lts.conf it is looking for the /var/lib/tftpboot/ltsp/i386/lts.conf
| |
13:00 | Does domeone know why is this?
| |
13:01 | <alkisg> gchaos: it receives the path from dhcp
| |
13:01 | I changed it so that it looks in the same directory as where it received the kernel, but I think it was after the stretch release
| |
13:02 | <gchaos> The path in the dhcp is right, the client boots the environment
| |
13:02 | <alkisg> Can you post your dhcp.conf so that I tell you what to change?
| |
13:02 | <gchaos> yes, I can, how can I post a file here?
| |
13:02 | <alkisg> Or, just use a symlink ln -s i386 office-i386-xfce4 in tftp, so that it finds it in both locations
| |
13:02 | !pastebin
| |
13:02 | <ltsp> pastebin: try !paste
| |
13:02 | <alkisg> !paste
| |
13:03 | <ltsp> paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
| |
13:04 | <gchaos> https://pastebin.com/PGq66KYE
| |
13:04 | If I use symlink ln -s i386 office-i386-xfce4 it will work
| |
13:04 | but it is not the right behaviour
| |
13:05 | lucascastro has joined IRC (lucascastro!~lucas@191.43.44.158) | |
13:05 | <gchaos> client should be loading lts.conf from the same directory where it loads its kernel file
| |
13:06 | <alkisg> Sure, I fixed that already,
| |
13:06 | the problem is that your dhcp.conf doesn't seem wrong
| |
13:07 | Can you run this on the client?
| |
13:07 | ipconfig -n eth0
| |
13:07 | <gchaos> sure
| |
13:07 | <alkisg> (or whatever eth0 is called)
| |
13:07 | <gchaos> ens3, sure
| |
13:07 | <alkisg> As root, and put the result to pastebin again
| |
13:07 | Ah, gchaos, are you using ipappend 3?
| |
13:08 | cat /proc/cmdline will tell you, if you see an ip=xxx there then you are
| |
13:08 | which means that the client doesn't do a dhcp request
| |
13:08 | <gchaos> BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/remoteos--vg-root ro quiet
| |
13:09 | sorry, should I run this command in the client, right
| |
13:09 | ?
| |
13:09 | I just did in the server
| |
13:10 | now from the client
| |
13:10 | BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/remoteos--vg-root ro quiet
| |
13:10 | <alkisg> we need from the client in both cases
| |
13:10 | !localxterm
| |
13:10 | <ltsp> localxterm: Any applications that you launch on a thin client actually runs on the server, not on the client itself. If you want to open a program on the client locally, you can type 'ltsp-localapps <program>' in a run dialog or in a terminal. For example, 'ltsp-localapps xterm' to open a terminal running on the client.
| |
13:10 | <gchaos> sorry, pasted wrong, wait a moment, let me get all the info you requested
| |
13:10 | it is a fat client, I installed xfce4 inside the chroot
| |
13:13 | lucascastro has left IRC (lucascastro!~lucas@191.43.44.158, Remote host closed the connection) | |
13:15 | <gchaos> have a look at my tcpdump
| |
13:15 | https://pastebin.com/CLTg7sPh
| |
13:15 | the last line, when getting lts.conf the path change
| |
13:16 | <alkisg> This is not the info i asked for
| |
13:16 | <gchaos> yes, sorry, I am still generating a new squashfs with net-tools to have ifconfig, sorry
| |
13:17 | <alkisg> no need
| |
13:17 | paste `cat /proc/cmdline`
| |
13:18 | ipconfig is at /usr/lib/klibc/bin/ipconfig
| |
13:18 | We don't need ifconfig
| |
13:18 | <gchaos> BOOT_IMAGE=vmlinuz-4.9.0-4-686 ro initrd=initrd.img-4.9.0-4-686 init=/sbin/init-ltsp quiet root=/dev/nbd0 BOOTIF=01-52-54-00-03-0f-32
| |
13:22 | ipconfig output is comming, I still had to enable root user in the squashsf image
| |
13:22 | ipconfig didnt let me run as normal user
| |
13:26 | Freejack has left IRC (Freejack!~quassel@unaffiliated/freejack, Quit: No Ping reply in 180 seconds.) | |
13:26 | <gchaos> https://pastebin.com/5HJ0BVVz
| |
13:27 | alkisg, ipconfig output https://pastebin.com/5HJ0BVVz
| |
13:28 | Freejack has joined IRC (Freejack!~quassel@unaffiliated/freejack) | |
13:35 | <alkisg> gchaos: it's strange then that the client asks for i386
| |
13:35 | Let me find the commit...
| |
13:37 | https://bugs.launchpad.net/ltsp/+bug/1594840
| |
13:37 | http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2742
| |
13:38 | gchaos: on the client, there's a /var/cache/ltsp/net-*.conf file
| |
13:38 | Can you put that to pastebin too?
| |
13:39 | And finally, put the client's /usr/share/ltsp/init-ltsp.d/05-getltsconffile
| |
13:39 | <gchaos> yes, sure
| |
13:43 | alkisg, net-ens3.conf https://pastebin.com/r8ihTEqr
| |
13:44 | alkisg, and, 05-getltsconffile https://pastebin.com/LEmvsJBe
| |
13:44 | <alkisg> gchaos: if you're not ....manually editing those files, something is wrong
| |
13:45 | The client sends "Linux ipconfig" which isn't PXEClient so the server should respond with nbi.img, not pxelinux.0
| |
13:45 | As it does in the ipconfig request
| |
13:45 | Ah ok got it
| |
13:45 | BOOT_IMAGE=vmlinuz-4.9.0-4-686 ro initrd=initrd.img-4.9.0-4-686 init=/sbin/init-ltsp quiet root=/dev/nbd0 BOOTIF=01-52-54-00-03-0f-32
| |
13:46 | This should be BOOT_IMAGE=/ltsp/office-i386-xfce4/vmlinuz...
| |
13:46 | <gchaos> so, it might be wrong in my pxelinux config?
| |
13:46 | <alkisg> That's what's configured wrong, your pxelinux.cfg
| |
13:47 | <gchaos> yes, I was configured automatically by ltsp scripts
| |
13:47 | let me check
| |
13:49 | you are right about nbd.img, I changed dhcp.conf file, while we were talking and rebooted my client, I wanted to check if would change anything
| |
13:49 | I am sorry
| |
13:51 | <alkisg> paste your pxelinux.cfg
| |
13:51 | <gchaos> for the past couple of weeks I have, several times, installed ltsp-server package only in Debian 9 (stretch) and built fat clients
| |
13:52 | 1 sec
| |
13:53 | <alkisg> why several times?
| |
13:54 | <gchaos> ecause I am documenting my findings, I want to undestand it, and after all, there is a throubleshooting section where. I want to post it on the web later
| |
13:55 | <alkisg> !ltsp-manager
| |
13:55 | <ltsp> ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
13:55 | <alkisg> This is the recommended way to install ltsp nowadays
| |
13:55 | <gchaos> ahhh ok :D
| |
13:55 | https://pastebin.com/WEMdVNd6
| |
13:58 | <alkisg> That's not normal ltsp installation, it doesn't contain the tftp paths
| |
14:00 | <gchaos> do you want me to generate it again using ltsp-update-kernel so we can see logs or anything else?
| |
14:00 | <alkisg> Did you modify update-kernels.conf/
| |
14:00 | ?
| |
14:00 | <gchaos> nope, not at all
| |
14:04 | <alkisg> be back in 10'...
| |
14:05 | <gchaos> don't worry, I have to go for ~40min, I will be back later
| |
14:06 | <alkisg> it's just a misconfiguration, different than the defaults
| |
14:07 | <gchaos> as I was saying, I did it several times and the results weren't all the same, for instance, the first few times I had this problem with nbd-server were I have to explicity config it to listen IPv4 leaving out IPv6
| |
14:07 | otherwise it would not allow IPv4 clients at all to connect
| |
14:08 | but then, this default behaviour changed and I don't need to do this configuration anymore and it works out of the box
| |
14:08 | now
| |
14:09 | I saw this behaviour (not allowing IPv4 clients to connect) listed as a bug, if I am not wrong published in January 2016
| |
14:12 | I still can't get consistent behaviour, that is also one of the reasons I installed it several times, I will still do it until I understand every thing problem, so, for the next days, if you area willing to try any new code, just let me know
| |
14:15 | <alkisg> Back
| |
14:16 | Well, I only really care about the new installation method for ltsp
| |
14:16 | gchaos: what is your tftpd-hpa configuration?
| |
14:17 | <gchaos> 1 sec
| |
14:17 | pasting it
| |
14:19 | https://pastebin.com/skGP9mEK
| |
14:20 | <alkisg> That looks fine too...
| |
14:22 | gchaos: ok, i was able to reproduce it
| |
14:23 | <gchaos> ahh good
| |
14:23 | I will be around during the day, let me know if you need anything else
| |
14:25 | and thank you very much for your help, I had no idea what was going on
| |
14:27 | just to let you know, when adding the repo you told me, I got this error https://pastebin.com/Sy6wgEW7
| |
14:30 | <alkisg> I commented in https://bugs.launchpad.net/ltsp/+bug/1594840
| |
14:31 | Only LTS Ubuntu releases are supported, bionic isn't even alpha yet
| |
14:31 | Put "xenial" as the release there
| |
14:32 | Although for debian, you'd want ltsp-manager from experimental
| |
14:32 | Not from the repository
| |
14:36 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
14:38 | <gchaos> ahh ok, thanks again :)
| |
14:51 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
14:52 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Remote host closed the connection) | |
14:55 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
15:14 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
15:44 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Remote host closed the connection) | |
15:44 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
16:32 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Ping timeout: 258 seconds) | |
16:32 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
16:33 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
16:49 | lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18) | |
16:50 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving) | |
16:59 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Quit: forum) | |
17:06 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
17:08 | lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Remote host closed the connection) | |
17:24 | Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
18:12 | lucascastro has joined IRC (lucascastro!~lucas@138.68.106.79) | |
18:17 | bergaliv has joined IRC (bergaliv!~habbe@185.94.192.199) | |
18:22 | bergaliv has left IRC (bergaliv!~habbe@185.94.192.199, Quit: Leaving) | |
18:35 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Remote host closed the connection) | |
18:36 | forum has joined IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at) | |
19:16 | forum has left IRC (forum!~Thunderbi@93-82-101-88.adsl.highway.telekom.at, Quit: forum) | |
19:37 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
19:59 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
20:03 | Mip has joined IRC (Mip!~Mip@208.72.71.69) | |
20:27 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
20:39 | kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:b834:80db:66e2:6ed0, Ping timeout: 255 seconds) | |
20:54 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 248 seconds) | |
21:18 | lucascastro has left IRC (lucascastro!~lucas@138.68.106.79, Ping timeout: 240 seconds) | |
21:28 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
21:33 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
23:09 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Quit: Ex-Chat) | |
23:09 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |