Explore >> Select a destination
|
You are here 
|
hjr265.me | ||
| | | | |
pboyd.io
|
|
| | | | | The flower bed in the front of my house. Yes, it's overgrown. I'm sure an upstanding citizen concerned with suburban respectability, such as yourself, will agree with my wife that I "should really do something about that." I had plenty of time this week, so naturally, I used that time to ignore the flower bed and write a mosaic generator. That way, I can give you this lovely mosaic of my not-so-lovely flower bed: | |
| | | | |
konradreiche.com
|
|
| | | | | Starting a goroutine is as easy as adding the go keyword in front of a method, but managing the lifecycle of a goroutine is not. If you only need to start a few goroutines and wait for their completion, you are off the hook thanks to sync.WaitGroup. However, what if a goroutine has to run for a specific duration or repeatatly in a loop until the initiating code terminates? Does it matter? After all, if the main goroutine terminates, any other goroutine will also stop. It does matter, because depending on what the goroutines are doing, it might leave your system in an inconsistent or invalid state. Channels are a commonly used to signal to a goroutine that it can shut down, but I often see the use of a signaling channel, for example chan bool or chan struct{}... | |
| | | | |
antonz.org
|
|
| | | | | Limiting the concurrency and waiting for the peers. | |
| | | | |
blog.oddbit.com
|
|
| | | There are many guides out there to help you configure your Linux system as an LDAP and Kerberos client to an Active Directory server. Most of these guides solve the problem of authentication by embedding a username and password into a configuration file somewhere on your system. While this works, it presents some problems: If you use a common account for authentication from all of your Linux systems, a compromise on one system means updating the configuration of all of your systems. If you don't want to ... | ||
