Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


uudruid74 last won the day on October 30 2015

uudruid74 had the most liked content!


  • Location
    Dallas, TX USA
  • Interests
    Tabletop RPG, Guitar, Linux, Eddon, raising penguins

Recent Profile Visitors

3,062 profile views

uudruid74's Achievements

  1. I checked the logs before and didn't see anything odd. But, now its stopped doing it. I'm thinking it was maybe a DNS thing. More about me at https://eddon.systems
  2. Both points are valid, but there aren't many other options. Maybe we need a package manager that installs new software based on pre-defined groups and makes new users members. More about me at https://eddon.systems
  3. I would just give separate accounts for play and school, for each kid. The play accounts would include an extra 'group' membership. The Linux firewall can restrict access to sites by the processes owning user and group. Application can have execute restricted if not in the owning group. You may need a fairly sophisticated firewall to scan the page for keywords like 'game', 'movie', 'porn' or whatever else you like. Some stuff always blacklisted, rest of the net locked except for whitelisted sites during school. And VNC should already be well integrated. Now, set up the 'play' accounts to be able to log in between certain times, and you can have a from job force the play accounts to log off when school starts. I would make the kid's school files accessible outside of school, but not the other way around. More about me at https://eddon.systems
  4. My website is tengine and joomla. There is a landing page (preloads some stupidly large javascript while you look at pretty animations) which has a link to the Joomla stuff (php via pfm) Joomla hangs the first time you go into it. If you refresh or hit enter in the URL bar, it comes right up. Happens on multiple clients. Anyone seen this before? More about me at https://eddon.systems
  5. Nevermind. I got it all working and it seems to work great. Way cool to have my mail sorted into folders before I ever open one of my email programs. Now I just need to move more of my mail to my own server. I'm loving this! :-) More about me at https://eddon.systems
  6. Anyone have a good HowTo for setting up DoveCot with Sieve filters? I'm more familiar with Courier, but I just took the plunge and migrated over. I have sieve and managesieve USE flags set. The web site for Dovecot starts talking about Pigeonhole. Do I need it? There isn't an ebuild for it, so if I need it, what are the USE flags for? I just don't see how this fits together and all I can find are a few undocumented posts of config files, and I refuse to blindly cut n paste, or instructions for Ubuntu that don't seem to apply to us. Any Dovecot experts? More about me at https://eddon.systems
  7. I don't think you need to bother with Metro. I remember the old Stage3 vs Stage1 wars on Gentoo (some 12 years ago now) and everyone will have their own thoughts. I like things to just work with a minimum of hassle. Just crab a stage3 and go. BTW, you use a lot of Gnome software. The Gnome desktop supports ALT+SUPER+8 to turn on zoom, ALT+SUPER+'=' for zoom in (the +/= key and use '-' next to it to zoom out again). And if you really have trouble the screen reader is ALT+SUPER+S (if orca is installed). There are others like text size and high contrast adjustments, but those don't seem to have hot keys press defined. More about me at https://eddon.systems
  8. Systemd is NOT supported by Funtoo. Get it off your machine. You don't need it for Funtoo's Gnome. Systemd on systems its supposed to work on does weird stuff like this. Trying to meld it with Funtoo OpenRC is asking for serious pain. More about me at https://eddon.systems
  9. Are you using a framebuffer console? More about me at https://eddon.systems
  10. Another similar tool to fail2ban is sshguard, but you might to just get a list of Chinese IPs and permanently block them all. More about me at https://eddon.systems
  11. There was a slashdot article about Busybox removing systemd support, which turned into an sub-thread about an ipv6 over ipv4 service. The systemd maintainers added a respawn "fix" that would restart the service within 10 seconds since the daemon would abort if the network wasn't up .... of course this means that the upstream service providers get hit with retries every 10 seconds if your password is wrong or something else is misconfigured, and they were annoyed that the warning NOT to respawn wasn't being acknowledged and no notification was given that the unit file was being changed. They site systemd as the problem for not verifying that the network is up before starting the service. The systemd folks site that this shouldn't be necessary since "modern" systems (he mentions his Apple Powerbook) have intermittent networking and the daemon should use exponential backoff if the network is down. The daemon author says people need to read the logs before restarting the daemon and the systemd guys say that users aren't admins and don't read logs! This is a classic example of what I see as the division of thought. The old-school admins see a server and classic start-up routines - you are started when networking comes up. If networking is down, abort. Read the logs. Auto-restart is bad. Systemd wants it easy and wants it to work on a laptop without thought (and apparently without a GUI tool that checks the log to decide if it should respawn), wants services to be restarted and says that the daemon author doesn't provide an exit code as to why the daemon stopped, so the only choice is to restart for all exits. He says the daemon is bi-polar because it will retry if the network is up when its started, but not other times, and sites network connectivity problems may not be local. Here's my take on this. Network down and can't connect are two different things. The former is a local issues and easy to detect. In this instance, the daemon can/should quit and log. Further, networking should be UP before the daemon is started. Specifically, the daemon should be started as a response to the "event" that the network is up. If there is a login problem or other issue, it should also abort and log. If the network is up, but you can't connect to the server, then use exponential backoff and retry. Systemd should know when network devices like Wifi disconnect and reconnect. It should also know if the daemon is running. It should start the daemon on the condition that the network has been brought up and it is not already running. Now ... what am I missing ??? Why would it start without networking being up? Why would anyone restart the service every 10 seconds? Sounds brain dead to me! Typical SysV init would run the network up/down scripts and get this right. Systemd SHOULD get this right, and I'm sure someone will say its been misconfigured or whatever, but notice two different mind-sets here. One person wants it to just work with focus on easy - and who cares what damage it may cause. The other person wants people to stop and read (no matter how unrealistic that may be). I once had someone tell me they couldn't print ... they said some error message kept popping up. I said, "What does it say?" They said, "I dunno". I said, "Well, try it again and read it!" And I could tell they were mad that I wouldn't run over there and fix their stupid Windows problem ... they did not want to read me any technical jargon from some error message on the screen! The response was, "Nevermind." ... WHAT? ... Guess what the Error said?
  12. I'm not really a fan of udisks either. Even after unmounting/ejecting a usb device, I can't fsck the thing because the kernel thinks its in use, even with no files open on it. I think this is a udisks issue, which is now a systemd thing. The workaround is to remove the device and reinsert it but don't open it or else udisks will hang on to it forever. These over-complicated system daemons are horrible. And they all seem to come from freedesktop.org ... I'm really starting to hate freedesktop.org. More about me at https://eddon.systems
  13. It doubt it will ever be an option, let alone the default.
  14. Or modify rc-update to look for systemd unit files? More about me at https://eddon.systems
  15. There would seem to an issue with fragmentation of our userbase. This will only get worse. It would be nice to abstract daemon installation in some portable way. Maybe some application that could convert from some universal configuration to whatever the local init system requires, or perhaps we should accept that systemd will be prevalent and make a converter that converts systemd configurations to openrc scripts? Does such a think already exist? More about me at https://eddon.systems
  • Create New...