By “Syslog-ng Engineer” do they mean a C systems programmer who can fix bugs and add features to syslog? that’s a rather different role from being an admin; even if, depending on the size of the operation, it make sense to give both roles to the same person

Besides Journal not being available on non-Linux, there are a could of reasons for using syslog: it can log to a remote server for instance. Journal does have a remote logging capability, but at best you have to run two log sinks in parallel, at worse it’s a non starter because everything that’s not a Linux box (network routers, VMware hosts, IDS appliances) can’t speak to it

Another is fine filing and retention. With syslog you can say things like “log NOTICE and above from daemon XYZ to XYZ.log and keep 30 days worth; log everything including DEBUG to XYZ-debug.log, keep no more than 10MB”. With Journal you rotate the entire log or nothing, at least last I looked I couldnt find anything finer. There are namespaces, but that doesn’t compowe, the application needs to know which log goes into which namespace

You clearly have more experience than I do; the only explanation for why my (one) attempt is not going so well is that I had less than ideal conditions. Both temperature and user technique, probably the latter is most to blame!..

It is pure oil, maybe I’m being too impatient then, a month is a long time though!

/u/NataliePortland@lemmy.ca suggested a wipe with solvent, is that the role of orange oil? I think ill try that when I have time in few days

It’s inside the house, but this being winter, is not super warm.

I disn’t do the two steps apply liberally, wipe the excess a few minutes later. Of well, top late to go back and do that :)

I think I’ll try your suggestion when I have time in a few days

CVS is the authoritative repository of code, and they recommend to users to use that or reposync (built atop of CVS) to keep their system updated.

There is also a GitHub mirror , and got is an OpenBSD project, and I suspect a number of devs use one of those for local work until it’s time to push the changes to the authoritative tree.

Justification I’ve heard is that if one part of the couple is managing the other, or is promoted after the relationship started, then:

• there is a power imbalance in the couple, possibly one is coercing the other (« I can’t leave him/her, they’ll make my worklife hell / get me fired »);
• there is a risk the manager will promote their partner even if their job performance doesn’t warrant it

Companies will want to both avoid this sort of things, and avoid being seen to enable this sort of things. They might want to move one of the parties to a different department so that the higher up one doesn’t make promotion decisions for the other.

I’ve once worked at a company that wanted to know about relationships between their employees and suppliers/customers’ employees, again because that might enable situations where a supplier / customer is treater favourably because of personal relationships