**** BEGIN LOGGING AT Fri Jan 18 02:59:57 2019
Jan 18 10:03:48 <sixwheeledbeast^> Slightly OT, anyone know much about MHL? Mobile HD Link
Jan 18 10:05:25 <Vajb> nope. Does anyone know why this happens after reboot?
Jan 18 10:05:28 <Vajb> ~ $ screen
Jan 18 10:05:28 <Vajb> Cannot make directory '/var/run/screen': Permission denied
Jan 18 10:06:03 <Vajb> if O create dir and one file it asks it works untill reboot
Jan 18 10:06:11 <Vajb> if i*
Jan 18 10:08:00 <sixwheeledbeast^> I'd guess permissions but I don't really use screen
Jan 18 10:08:52 <sixwheeledbeast^> https://linux.die.net/man/1/screen
Jan 18 10:09:56 <inz> Sounds like volatile /var/run but no init script to create the dir on startup
Jan 18 10:11:26 <sixwheeledbeast^> debug or log commands help?
Jan 18 10:11:33 <inz> (or tmpfiles.d entry on systemd systems)
Jan 18 10:13:20 <Vajb> is var/run wiped on every boot?
Jan 18 10:13:53 <inz> Or it could be a tmpfs, so it's simply not stored anywhere
Jan 18 10:14:53 <Vajb> so basically I just need a script to make that said dir and file before screen starts
Jan 18 10:15:15 <inz> Or just create the dir with correct permissions
Jan 18 10:15:28 <sixwheeledbeast^> touch dir
Jan 18 10:15:30 <sixwheeledbeast^> ^
Jan 18 10:15:51 <inz> For example in debian screen is setguid utmp, and the screen dir is group writable for utmp
Jan 18 10:16:18 <Vajb> I made dir last time I used screen but it was lost in reboot
Jan 18 10:16:43 <inz> Yeah, I meant make the script create the dir with the perms
Jan 18 10:16:51 <inz> Unclear comms, sry
Jan 18 10:17:42 <Vajb> okay, same message different phrasing :)
Jan 18 21:13:18 <Vajb> interesting. My device went to state where pnatd didn't take any commands. Reboot was the only solution.
**** ENDING LOGGING AT Sat Jan 19 02:59:56 2019