Sponsored Content
The Lounge What is on Your Mind? Announcement: New Discourse Site to Go Live this Weekend Post 303045452 by Neo on Tuesday 24th of March 2020 10:19:36 PM
Old 03-24-2020
On another note:

I have had a few people comment about converting new site to www.unix.com versus community.unix.com, so let me remind everyone:

This site has over 200K man pages and none of the man pages migrate to the new forum (anytime soon, we may write a plugin for this sometime in the future, however).

So, this site has a lot of reference material which is very important, including man pages and code.

In some instance, the migration of legacy posts with code from here to discourse has results in instances of "code mangling" where, for example, the original vB4 to Discourse migration script changed new lines chars "\n" to hard line breaks in code fragements.

Our moderator (and Poster of the Year 2019 as well), Scrutinizer is working on perfecting this Ruby script and when he is done; we will test this on a staging site and then update all the posts on the new site.

Even when the new site reaches "perfection" (or 99.9..., whatever that means), this site has a tremendous amount of important reference material (man pages, original code, etc).

So, eventually we will turn this site into a reference site and keep the reference site available. However, this "conversion to a reference site" is going to happen slower than we originally thought because of some parsing errors we found (we can all thank Scrutinizer for this, looking carefully at code) in the original Discourse Ruby vbulletin.rb script.

Frankly, after working 14 days in a row, 12 hours a day, on this migration, I was disappointed to learn of the errors in the original vbulletin.rb script; but I'm glad we found them and we all owe a debt of gratitude to Scrutinizer for working on modifying the preprocessing routine of the original Discourse vbulletin.rb migration script.

Thank you Scrutinizer!!

Regarding updating the posts:

After we have fully tested the new preprocessing routine on a staging site, we will update the posts on the discourse site. Discourse keeps both the raw (preprocessed) and cooked (post-processed) text for each post in the DB. We will update the raw posts and recook them when it is time to do the rebaking.

Because of this hard line break issue for the "\n" char in code fragments, Scrutinizer is looking at more enhancements to preprocessing at the same time.
 

5 More Discussions You Might Find Interesting

1. Web Development

Setting up Development and Live web site environment

Hi, I am fairly new to unix so please go easy on me.. I have a VPS on which I would like to setup a development and live web site environment and can't seem to work out what is the best technique for doing so. I would like to be able to mirror the live site and have a "check out" and... (0 Replies)
Discussion started by: ciantrius
0 Replies

2. IP Networking

How to establish site to site vpn - Linux machine and cisco asa?

Hi, I am trying to establish vpn between my linux server and cisco asa at client side. I installed openswan on my cent os. Linux Server eth0 - 182.2.29.10 Gateway - 182.2.29.1 eth1 - 192.9.200.75 I have simple IPtables Like WAN="eth0" LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies

3. IP Networking

Does cisco 1921 router support site to site VPNs using IPSec?

Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? " A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies

4. IP Networking

IPSec Openswan Site to Site VPN - Big Pain

Hi @all, I try to connect 2 LANs with IPSec/Openswan LAN 1: 192.168.0.0/24 LAN 2: 192.168.1.0/24 This is my Config: conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies

5. What is on Your Mind?

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates" The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
CHECKSENDMAIL(8)					    BSD System Manager's Manual 					  CHECKSENDMAIL(8)

NAME
checksendmail -- verify sendmail address transformations. SYNOPSIS
checksendmail [-a] [-d] [-b] [-C file.cf] [-b sendmail_binary] [-l log_file] [-r resolve] [-T test.address] DESCRIPTION
The checksendmail program is a perl script that aids the testing of sendmail(8) 's various configuration files. checksendmail passes typical addresses (supplied in input files) through sendmail and prints the results of the resolution and transformation routines. The input files contain a list of addresses, one per line. For example: user user@site user@site.com The input file can contain comments started with a # and blank lines. OPTIONS
-a Show aliasing of local addresses in mail address resolution phase of testing -d Preceed each address translation line with ruleset sequence summary -C file.cf Use the sendmail configuration file file.cf instead of the default /etc/sendmail.cf file. -b sendmail_binary Use the specified sendmail_binary as the path to invoke sendmail (instead of /usr/sbin/sendmail). -l log_file Log sendmail address test mode debugging output to log_file -r resolve Use resolve as the input file for the addresses to be used for mail resolving. Defaults to address.resolve. -T test.address Use test.address as the single address to test. Cannot be used in conjunction with file setting flags. EXAMPLES
The following command will pass the addresses in address.resolve through sendmail using the configuration information in myconfig.cf. example% cat address.resolve user user@site user@site.com example% checksendmail -C myconfig.cf system: myhost.gadget.com current dir: /tmp/Checksendmail resolve file: address.resolve sendmail binary: /usr/sbin/sendmail sendmail version: 8.9.3 config file: /etc/sendmail.cf config file version: V8/Berkeley Mail address resolution user --(ether )--> user[rmtc] user@site --(ether )--> user@site[rmtc] user@site.com --(ether )--> user@site.com[rmtc] `To' address transformations for mailer ether: user ----> user user@site ----> user@site user@site.com ----> user@site.com `From' address transformations for mailer ether: user ----> user user@site ----> user user@site.com ----> user The first section of the output shows how the addresses in the input files are resolved by sendmail(8). Consider the following output line: user@site.com --(ether )--> user@site.com[rmtc] The input address user@site.com resolves to use the ether mailer. That mailer is directed to send the mail to to the user user@site.com at site rmtc (as indicated in the square brackets). The two later sections of output show how the addresses specified as the To and From address are transformed in the text of the headers. In the example above, the To addresses are untouched. The From addresses, however, all lose their machine information on the way through the mailer: user@site ----> user This may be desirable when using a configuration file on a workstation which is to be hidden as a mailhost from the rest of the network. The following is a set of addresses used at one site for the purposes of testing address resolution. Comments after the addresses detail why particular addresses are present: user Standard trivial address user@rmtc qualified at one level user@rmtc.central qualified at two levels user@rmtc.central.sun.com qualified all the way rmtc!user local but specified as uucp user@summit a workstation (normally delivered locally, though) user@summit.central same but more qualified user@summit.central.sun.com same but fully qualified summit!user same but specified as uucp user@prisma Backward compatibility tests user@prisma.com prisma!user user@central Superior domain testing user@machine.central more qualified, but unknown user@summit.central more qualified and known user@eng name in faraway domain user@machine.eng unknown machine in faraway domain user@summit.eng local machine, far away domain user@hoback far away machine user@machine apparently local but unknown machine user@sun.com Standard trivial address user@machine.dom.sun.com fully qualified but unknown machine user@foo.com standard, known, really far away domain user@foo.dom standard, unknown, really far away domain site!user Single level uucp site1!site2!user Double level uucp user@foo.dom@bar.dom Trickier address site!user@foo.dom Mixed uucp/domain site!user@uunet.uu.net Mixed double uucp/domain NOTES
Note that checksendmail is a perl script. If your site does not have perl(1), it can be obtained via anonymous ftp from ftp.uu.net. sendmail requires that the user have access to directory specified by the OQ parameter in the configuration file (normally /usr/spool/mqueue). checksendmail verifies that the user has access to this directory before allowing the test to continue. AUTHORS
Gene Kim Rob Kolstad Jeff Polk Modified by Robert Harker SEE ALSO
sendmail(8) BSD
November 14, 2000 BSD
All times are GMT -4. The time now is 06:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy