search for: _force_

Hello, For some reason, I thought little about the "clear" command today.. Let's say a privileged user (root) logs on, edit a sensitive file (e.g, a file containing a password, running vipw, etc) .. then runs clear and logout. Then anyone can press the scroll-lock command, scroll back up and read the sensitive information.. Isn't "clear" ment to clear the

...t;> "EvtHandler":evthandler.html </span><span class="lines">@@ -432,8 +419,8 @@ </span><span class="cx"> </span><span class="cx"> h4. Parameters </span><span class="cx"> </span><del>-* _force_ @false@ if the window''s close handler should be able to veto the destruction -of this window, @true@ if it cannot. </del><ins>+* _force_ @false@ if the window''s close handler should be able to veto + the destruction of this window, @true@ if it cannot. </ins>&lt...

..."aggressively" go to the journal, journal mis-reads can _toast_ a filesystem. I'll take a full fsck that _always_ works to a jounaling filesystem that aggressively goes to the journal, or has unproven recovery tools. I have experienced this on NTFS many times. To the point where I _force_ a CHKDSK anyway, on any improper shutdown (effectively negating the benefit of a JFS). NTFS is based on IBM's OS/2 HPFS, so this isn't just a Microsoft design mentality (as HPFS follows some of the same logic). 3rd party sources (i.e. could be heresy) says IBM's JFS follows this &quot...

https://bugzilla.mindrot.org/show_bug.cgi?id=2713 Bug ID: 2713 Summary: Please provide a StrictModes-like setting (command line parameter) for ssh (client) Product: Portable OpenSSH Version: 7.5p1 Hardware: Other OS: Other Status: NEW Severity: enhancement Priority: P5

Hi, I'd like to use a flash drive as a journal device, with the purpose of keeping the main disk drive spun down as long as possible. I have a couple of questions: 1) Does the journaling code spread write accesses to the journal device evenly, as I hope, or are there blocks that are particularly "hot"? I.e., do I have to worry about the flash device dying quickly because of

https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau