deactivate command periodically is one way to prevent the This simulated user activity will re-start the countdown (so, issuing the If the screen is locked, then the passwordĭialog will pop up first, as usual. This command will cause the screen to un-blank as if there had been This means that if the screensaver is active (the screen is blanked), then deactivate This tells xscreensaver to pretend that there has just been user activity. The user had been idle for long enough.) The screensaver will deactivateĪs soon as there is any user activity, as usual. activate Tell xscreensaver to turn on immediately (that is, blank the screen, as if quiet Only print output if an error occurs. Options: -help Prints a brief summary of command-line options. Xscreensaver-command accepts the following command-line The xscreensaver-command program controls a running | -prev | -select n | -lock | -suspend | -exit | -restart |
[-help | -quiet | -verbose | -activate | -deactivate | -cycle | -next My personal favorite is Source Mage, a source based distribution, with its package manager called Sorcery.Xscreensaver-command - control a running xscreensaver process SYNOPSIS
#Linux xscreensaver strange install
Ubuntu is kind of an exception, but if you take a look at some of the major distributions, the software which install programs is not named from nowhere: openSUSE uses the command “zypper,” Fedora and CentOS share the Yum package manager, Archlinux prefers Pacman and Yaourt, PuppyLinux works with PET packages, Sabayon uses Equo, etc. But Linux developers also like to give strange names to their system, and especially to the package manager of their distribution. If you tried TTYtter, the software to tweet from the command line, you may have seen some jokes in the documentation. In general, developers have their own sense of humor. But beware, because in most cases, you will be the one to get the insults more than any intruder. But this is an extreme case and there are two easy solutions to prevent that: ask the parent to kill its zombie child withĪnd that’s all! Now, at every missed password, the system will find a new way to “ encourage” the intruder. Since a 32-bit system is limited to 32767 PIDs, if you have too many zombies, you will be unable to launch anything. The only problem it can create is in case of huge proliferation. Well, in fact, a zombie does not affect your system.
Of course, it is no use trying to kill such a process: it is already dead (see the humor there?). But sometimes, the parent process does not do its job properly and its child stays as a zombie. Normally, after killing a process, its status become EXIT_ZOMBIES, and it will be removed from the process list. A zombie process is exactly what is sounds like: the remnant of a bug or a poorly programmed software which makes a supposedly killed process stay around. There is another funny case about processes, it is called zombie process. If you want to see it by yourself, Xscreensaver has an option in its menu called “Kill the daemon.” Now, if you appreciate RPG like I do, you should be more receptive. However, you should also know that a process which is launched at boot is called a “daemon.” Still not smiling? OK, what happens when you want to terminate a process that has been launched at boot? Yes, you kill a daemon. It is crude, and kind of funny in itself, but no one perceives the humor anymore because it is so widespread. You probably know that we do not “terminate” a process in Linux.
0 kommentar(er)
