20210528 - a Slackware upgrade causes the page rendering to fail. Apologies and I am looking for the cause.
Reported as https://forum.dokuwiki.org/d/19270-dokuwiki-instance-no-longer-rendering-some-syntax-correctly

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
slackbook:process_control [2012/09/08 21:29 (UTC)]
kikinovak [ps] fixed misspelling ("equivalent", not "equivilant")
slackbook:process_control [2012/10/02 00:22 (UTC)]
mfillpot [cron] removed base xml
Line 17: Line 17:
  
  
-<code>+<code bash>
 darkstar:~$ ps darkstar:~$ ps
   PID TTY          TIME CMD   PID TTY          TIME CMD
Line 45: Line 45:
  
  
-<code>+<code bash>
 darkstar:~$ ps -e darkstar:~$ ps -e
   PID TTY          TIME CMD   PID TTY          TIME CMD
Line 75: Line 75:
 </note> </note>
  
-<code>+<code bash>
 darkstar:~$ ps aux darkstar:~$ ps aux
 USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
Line 103: Line 103:
  
  
-<code>+<code bash>
 darkstar:~$ ps -o cmd -o etime $$ darkstar:~$ ps -o cmd -o etime $$
 CMD                             ELAPSED CMD                             ELAPSED
Line 122: Line 122:
  
  
-<code>+<code bash>
 darkstar:~$ ps -o cmd -o rss -o vsz $(pgrep httpd) darkstar:~$ ps -o cmd -o rss -o vsz $(pgrep httpd)
 CMD                           RSS    VSZ CMD                           RSS    VSZ
Line 155: Line 155:
  
  
-<code>+<code bash>
 darkstar:~$ ps -ejH darkstar:~$ ps -ejH
 ... many lines omitted ... ... many lines omitted ...
Line 186: Line 186:
  
  
-<code>+<code bash>
 darkstar:~$ pstree darkstar:~$ pstree
 init-+-atd init-+-atd
Line 244: Line 244:
  
  
-<code>+<code bash>
 darkstar:~$ kill -l darkstar:~$ kill -l
  1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL  1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
Line 267: Line 267:
  
  
-<code>+<code bash>
 darkstar:~$ killall bash # SIGTERM darkstar:~$ killall bash # SIGTERM
 darkstar:~$ killall -s 9 bash # SIGKILL darkstar:~$ killall -s 9 bash # SIGKILL
Line 285: Line 285:
  
  
-<code>+<code bash>
 darkstar:~$ top darkstar:~$ top
 top - 16:44:15 up 26 days,  5:53,  5 users,  load average: 0.08, 0.03, 0.03 top - 16:44:15 up 26 days,  5:53,  5 users,  load average: 0.08, 0.03, 0.03
Line 321: Line 321:
 ===== cron ===== ===== cron =====
  
-<title>cron</title>+
  
 Ok, so we've learned many different ways of viewing the active Ok, so we've learned many different ways of viewing the active
Line 351: Line 351:
  
  
-<code>+<code bash>
 darkstar:~$ crontab -e darkstar:~$ crontab -e
 # Keep current with slackware # Keep current with slackware
Line 361: Line 361:
 to understand at first, so let's look at each part individually. From to understand at first, so let's look at each part individually. From
 left to right, the different sections are: Minute, Hour, Day, Month, left to right, the different sections are: Minute, Hour, Day, Month,
-Week Day, and Command. Any asterisk <key>*</key> entry matches+Week Day, and Command. Any asterisk <key>'*'</key> entry matches
 every minute, hour, day, and so on. So from the example above, the every minute, hour, day, and so on. So from the example above, the
 command is //"/usr/local/bin/rsync-slackware64.sh 1>/dev/null 2>&1"//, and command is //"/usr/local/bin/rsync-slackware64.sh 1>/dev/null 2>&1"//, and
Line 375: Line 375:
  
  
-<code>+<code bash>
  
 # Redirect everything to /dev/null with: # Redirect everything to /dev/null with:

In Other Languages
QR Code
QR Code slackbook:process_control (generated for current page)