User talk:Balsa - Revision history

Balsa: /* Editing Resource Limits page */ new section

2011-08-17T00:05:34Z

Editing Resource Limits page: new section

← Older revision		Revision as of 00:05, 17 August 2011
Line 305:		Line 305:

	--[[User:Balsa\|Balsa]] 02:26, 23 February 2011 (EST)		--[[User:Balsa\|Balsa]] 02:26, 23 February 2011 (EST)

			== Editing Resource Limits page ==

			Having recently run into some limits issues myself (and spending an hour or two learning about them), I am going to revise and extend the original [[Resource_Limits]] page. <br>
			Current goals:
			<ul>
			<li>Clarify where the ulimit documentation is. Slackware 12.2.0 (at least) has only a programmer's man page for ulimit. The shell builtin is documented in the shell's own man page.</li>
			<li>Steer users away from any programming manual pages. The above man page [ULIMIT(3)] says, "POSIX.1-2008 marks ulimit() as obsolete." This is potentially confusing; users may try to use non-existent getrlimit commands.</li>
			<li>ULIMIT(3) also says: "Warning: This routine is obsolete. Use getrlimit(2), setrlimit(2), and sysconf(3) instead. For the shell command ulimit(), see bash(1)." Same issue as above." </li>
			<li>Clarify whether or not ulimit is a shell builtin by letting the user test for it; if it is builtin, then matters become somewhat shell-specific.</li>
			<li>Expand the scope of the original article beyond increasing the limit for open files.</li>
			<li>Add a new section pointing to the README.limits file (as provided by the shadow package) as an alternate way of dealing with limits.</li>
			</ul>

			[[User:Balsa/Resource_Limits_Working_Draft\|Resource Limits Working Draft]]
			--[[User:Balsa\|Balsa]] 19:05, 16 August 2011 (CDT)

Balsa: Added link to sandbox.

2011-04-08T09:02:03Z

Added link to sandbox.

← Older revision		Revision as of 09:02, 8 April 2011
Line 289:		Line 289:

	--[[User:Balsa\|Balsa]] 13:38, 21 February 2011 (EST)		--[[User:Balsa\|Balsa]] 13:38, 21 February 2011 (EST)

			A [[User:Balsa/Sandbox\|sand-filled box]] labelled "Testing"
			--[[User:Balsa\|Balsa]] 05:02, 8 April 2011 (EDT)

	== NTP log file configuration documentation ==		== NTP log file configuration documentation ==

Balsa: /* ALSA */ jack UDP draft added

2011-03-20T05:47:30Z

ALSA: jack UDP draft added

@@ Line 73: / Line 73: @@
 Sample Encoding: 8-bit Unsigned Integer PCM<br/>
 OK, it plays as unsigned 8bit.  Success.<br/>
 == Simple tests from command line ==

Balsa: /* NTP log file configuration documentation */ new section

2011-02-23T07:26:21Z

NTP log file configuration documentation: new section

← Older revision		Revision as of 07:26, 23 February 2011
Line 252:		Line 252:

	--[[User:Balsa\|Balsa]] 13:38, 21 February 2011 (EST)		--[[User:Balsa\|Balsa]] 13:38, 21 February 2011 (EST)

			== NTP log file configuration documentation ==

			look for /usr/share/doc/ntp-doc/html/ntpd.html<br>
			It may be in a different place.<br>
			Use a http reader, like lynx to view it.<br>
			Go to "The Configuration File", then "Miscellaneous Options".<br>

			Scroll down to the "logconfig" and "logfile" headings.<br>

			There you will find a way to eliminate the "kernel time sync status change 6001" messages from syslog.<br>

			--[[User:Balsa\|Balsa]] 02:26, 23 February 2011 (EST)

Balsa: /* Sandbox and/or Editing Help pages on slackwiki? */ new section

2011-02-21T18:38:57Z

Sandbox and/or Editing Help pages on slackwiki?: new section

← Older revision		Revision as of 18:38, 21 February 2011
Line 246:		Line 246:

	--[[User:Balsa\|Balsa]] 13:34, 21 February 2011 (EST)		--[[User:Balsa\|Balsa]] 13:34, 21 February 2011 (EST)

			== Sandbox and/or Editing Help pages on slackwiki? ==

			If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know. If not, I might try to create one. Advice welcome.<br>

			--[[User:Balsa\|Balsa]] 13:38, 21 February 2011 (EST)

Balsa: /* Redirecting stderr and stdout to a file */ new section

2011-02-21T18:34:55Z

Redirecting stderr and stdout to a file: new section

← Older revision		Revision as of 18:34, 21 February 2011
Line 238:		Line 238:

	--[[User:Balsa\|Balsa]] 13:23, 21 February 2011 (EST)		--[[User:Balsa\|Balsa]] 13:23, 21 February 2011 (EST)

			== Redirecting stderr and stdout to a file ==

			/bin/true &> foo<br>

			This may be helpful in the "Piping" section here on slackwiki.<br>

			--[[User:Balsa\|Balsa]] 13:34, 21 February 2011 (EST)

Balsa: /* Getmail */ new section

2011-02-21T18:23:27Z

Getmail: new section

← Older revision		Revision as of 18:23, 21 February 2011
Line 224:		Line 224:

	--[[User:Balsa\|Balsa]] 13:17, 21 February 2011 (EST)		--[[User:Balsa\|Balsa]] 13:17, 21 February 2011 (EST)

			== Getmail ==

			One of getmail's biggest features is writing directly to Maildir. This obviates the need for a Mail Transport Agent (MTA).<br>

			In a getmail configuration file:

			[destination]<br>
			type = Maildir<br>
			path = ~/Maildir/<br>

			This will write your email directly to the ~/Maildir/ directory in Maildir format.<br>

			--[[User:Balsa\|Balsa]] 13:23, 21 February 2011 (EST)

Balsa: /* Octave: simple functions */ new section

2011-02-21T18:17:52Z

Octave: simple functions: new section

← Older revision		Revision as of 18:17, 21 February 2011
Line 164:		Line 164:

	Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.		Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

			== Octave: simple functions ==

			Find the Octave tutorial by typing doc at the Octave command line.<br>
			Navigate to * Introduction:: A brief introduction to Octave.<br>
			Then go to * Simple Examples::<br>
			The tutorial is quite brief, and gives few examples of functions.<br>
			This page will demo how to make simple functions, and how to call one function from another.<br>

			octave:11> function fn = fn ( p )<br>
			> fn = p*20<br>
			> endfunction<br>

			octave:10> function sn = sn ( a )<br>
			> sn = a * (1/2)<br>
			> endfunction<br>

			octave:12> function tn = tn( p, a )<br>
			> tn = sn(a)+fn(p)<br>
			> endfunction<br>

			octave:17> function excess = excess( p, a, bs )<br>
			> excess = bs - tn(p,a)<br>
			> endfunction<br>

			octave:18> excess(p,a,bs)<br>
			sn = 517.50<br>
			fn = 2140<br>
			tn = 2657.5<br>
			excess = -1452.5<br>
			ans = -1452.5<br>

			octave:28> function trade = trade ( p, a, bs, lt )<br>
			> trade = excess(p,a,bs)/lt<br>
			> endfunction<br>

			octave:26> function newacres = newacres (p, a, bs, lt, na )<br>
			> newacres = a+trade(p,a,bs,lt)<br>
			> endfunction<br>

			octave:36> p=107; a=1013; bs=3017; lt=25;<br>
			octave:37> newacres(p,a,bs,lt,na)<br>
			sn = 506.50<br>
			fn = 2140<br>
			tn = 2646.5<br>
			excess = 370.50<br>
			trade = 14.820<br>
			newacres = 1027.8<br>
			ans = 1027.8<br>
			octave:38> p=114; a=1027; bs=3095; lt=23;<br>
			octave:39> newacres(p,a,bs,lt,na)<br>
			sn = 513.50<br>
			fn = 2280<br>
			tn = 2793.5<br>
			excess = 301.50<br>
			trade = 13.109<br>
			newacres = 1040.1<br>
			ans = 1040.1<br>

			--[[User:Balsa\|Balsa]] 13:17, 21 February 2011 (EST)

Balsa: /* Exim - local mail only - setup and testing */ new section

2011-02-20T22:24:21Z

Exim - local mail only - setup and testing: new section

← Older revision		Revision as of 22:24, 20 February 2011
Line 92:		Line 92:

	--[[User:Balsa\|Balsa]] 16:15, 20 February 2011 (EST)		--[[User:Balsa\|Balsa]] 16:15, 20 February 2011 (EST)

			== Exim - local mail only - setup and testing ==

			Setup: not written yet.



			Testing / Debugging:

			The following are draft quality only.
			ps -efw \| grep -i -e exim \| grep -v grep
			#Lists running exim processes.
			netstat --inet -anp \| grep -i -e exim -e 25 -e mail
			#See if anything is listening on port 25.


			ls -l /var/log
			look for mail or exim4 directory, and mail.??? and mail.???? files.

			ls -l /var/
			look for mail, queue, or spool.
			Do a ls -l in any directories found above.

			Mail might be in ~/Mail

			Read the Mutt HOWTO on slackwiki.org.

			Read the qmail HOWTO as well.

			tail -f /var/log/exim4/mainlog (if it exists)
			The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
			There are numerous guides for screen. My suggestion is to printout the most common commands on paper and keep it near your monitor.


			Try the mail command out.
			man mail

			echo "Testing local mail, sent on `date` to the local system" \
			\| mail -s "Test of Local Mail" username@localhost.localdomain

			Note that username@localhost.localdomain may not work.

			Try hostname --fqdn

			look in /etc/hosts


			Testing the MTA with telnet on a certain port:

			telnet localhost 25

			HELO localhost

			MAIL FROM: username@localhost.localdomain

			RCPT TO: username@localhost.localdomain

			DATA

			SUBJECT: Testing mail via telnet

			This is the message body.

			Check if it worked with your favorite mail reader or by
			looking in the files listed above.
			End message body with a "." on a line by itself.
			.

			QUIT


			Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

Balsa: /* Simple tests from command line */ new section

2011-02-20T21:15:06Z

Simple tests from command line: new section

← Older revision		Revision as of 21:15, 20 February 2011
Line 73:		Line 73:
	Sample Encoding: 8-bit Unsigned Integer PCM<br/>		Sample Encoding: 8-bit Unsigned Integer PCM<br/>
	OK, it plays as unsigned 8bit. Success.<br/>		OK, it plays as unsigned 8bit. Success.<br/>

			== Simple tests from command line ==

			netstat - man netstat

			look for services that you don't know, read their manual pages. See if the service would be better listening to fewer interfaces [like localhost]. Use the ps command to figure out what's running. Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

			look at /etc/fstab

			man fstab
			man mount

			Read a security article [fixme] about this file and the options. Skim the LVM and partitions pages here on slackwiki. Read about the noexec option (don't use this without understanding the consequences)

			Try "hostname --fqdn" and see what it does. Check the exim page or qmail page to see about local mail delivery. Some security tools (and other stuff too) will email you when important events occur.

			Read about the sudo and su commands.

			--[[User:Balsa\|Balsa]] 16:15, 20 February 2011 (EST)