code logs -> 2021 -> Wed, 04 Aug 2021< code.20210803.log - code.20210805.log >
--- Log opened Wed Aug 04 00:00:50 2021
01:02 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
01:31 [R] [rs@Nightstar-d7h8ki.org] has joined #code
01:31 mode/#code [+ao [R] [R]] by ChanServ
01:35 Yossarian [soryu@Nightstar-d7h8ki.org] has joined #code
02:12 Degi [Degi@Nightstar-5gtv7r.pool.telefonica.de] has quit [Operation timed out]
02:12 Degi [Degi@Nightstar-c4osbc.pool.telefonica.de] has joined #code
04:32
<&McMartin>
"wow, 230 - 220 * 0.5 = 5!"
05:42
< catalyst>
hm
05:43 VirusJTG_ [VirusJTG@Nightstar-0th.oti.104.208.IP] has quit [Connection closed]
05:44 VirusJTG_ [VirusJTG@Nightstar-0th.oti.104.208.IP] has joined #code
05:47 Kindamoody[zZz] is now known as Kindamoody|afk
09:11 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
09:11 mode/#code [+qo Vornicus Vornicus] by ChanServ
11:01
< Yossarian>
hmmm
11:08
< Yossarian>
file locking mechnaisms on linux like systems are generally poor across processes?
11:09
< Yossarian>
what are some solutions to such a thing?
11:13
< Yossarian>
i mean there are advisory locks but
11:15 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
11:23
< Yossarian>
perhaps this is why my bash history is always inaccurate across gnu screen and tmux?
11:23
< Yossarian>
they all have their own copies in memory
11:37
< Yossarian>
or a lock file
11:38
<&[R]>
Bash doesn't write to the history file until it closes
11:38
<&[R]>
File locks have /zero/ to do with this
11:38
< Yossarian>
i was thinking of an abstract problem
11:39
< Yossarian>
but hard file locks seem silly
13:05 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
13:05 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection closed]
13:06 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
13:23 catalyst [catalyst@Nightstar-r73i9t.dab.02.net] has joined #code
13:26 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds]
13:58
<&ToxicFrog>
Yeah, there are various gross hacks you can do to get history syncing across bash sessions but it's not an out of the box feature like it is in zsh.
14:03
<&ToxicFrog>
Re file locking on linux, linux does support sysv mandatory locks (if a file has the setgid bit set and the gx bit unset locks on it are mandatory rather than advisory), for filesystems mounted with the `mand` option
14:03
<&ToxicFrog>
However, it applies only to fcntl/lockf (not to flock) and has known race conditions that make it not 100% reliable
14:04
<&ToxicFrog>
Generally locks on linux/UNIX are a way for different processes of the same program to avoid stepping on each other, not a way for one program to protect its data from outside interference./
17:19 ErikMesoy1 [Bruker@Nightstar-denh1k.bb.online.no] has joined #code
17:20 ErikMesoy [Bruker@Nightstar-denh1k.bb.online.no] has quit [NickServ (RECOVER command used by ErikMesoy1)]
17:20 ErikMesoy1 is now known as ErikMesoy
17:20 mode/#code [+o ErikMesoy] by ChanServ
17:27 catalyst_ [catalyst@Nightstar-4d0t03.dab.02.net] has joined #code
17:29 catalyst [catalyst@Nightstar-r73i9t.dab.02.net] has quit [Ping timeout: 121 seconds]
18:20 Kindamoody|afk is now known as Kindamoody
20:18 abudhabi [abudhabi@Nightstar-nu3815.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
20:21 gnolam [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has quit [[NS] Quit: Reboot]
20:23 abudhabi [abudhabi@Nightstar-mlpjsd.adsl.tpnet.pl] has joined #code
20:26 gnolam [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has joined #code
20:26 mode/#code [+o gnolam] by ChanServ
21:41 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
23:25 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Thu Aug 05 00:00:06 2021
code logs -> 2021 -> Wed, 04 Aug 2021< code.20210803.log - code.20210805.log >

[ Latest log file ]