Sponsored Content
Full Discussion: openserver 5.0.6 media need
Operating Systems SCO openserver 5.0.6 media need Post 302583600 by h0tw1r3 on Tuesday 20th of December 2011 11:26:13 PM
Old 12-21-2011
I'm in the same boat. Looking to redo an ancient (and quite fubar) install of 5.0.4. I'd prefer not to shell out $$ for 5.0.7v. From what I understand a 5.0.4 license works up to 5.0.6.

As for the email, wish I could. I'm a long time lurker with not enough posts to PM or email Smilie
 

10 More Discussions You Might Find Interesting

1. SCO

Openserver 6.0.0

I spent last weekend building a new system for a client. The old (current production) system is an Acer Altos G700 with 512mb memory, dual P4 2.4ghz processors, dual channel LSI RAID controller with 4 72gb Seagate disks. This system runs SCO 5.0.7 with MPX and all the patches applied. The test... (4 Replies)
Discussion started by: jgt
4 Replies

2. SCO

Looking for openserver 5.0.5 media kit

Hello We are running a pretty old system here which needs to be re-installed. Unfortunately even if all my licences are okay, my install CD are missing in the box. I contacted sco in order to get these media kit, with no luck (product discontinued) I was wondering if some good pal would... (5 Replies)
Discussion started by: qube001
5 Replies

3. SCO

OpenServer 5.0.6 Media Needed

I have a client with 5.0.6 who wants to migrate to new hardware. We have in our posession all appropriate paper software licenses. Over the years the media has vanished Can anyone assist with locating an ISO or actual CD containing OpenServer 5.0.6, please? Thank you (9 Replies)
Discussion started by: theantisco
9 Replies

4. SCO

SCO Unix OpenServer 5.0.5 Media Kit

My client has lost the SCO OS 5.0.5 install media. However, they do have a working SCO 5.0.5 system, but is crumbling apart. Where can I find the SCO OS 5.0.5 install media? Or can I get a copy of the SCO CD as a ISO file? Your help is much appreciated. (7 Replies)
Discussion started by: chedlee88-1
7 Replies

5. Fedora

media server?

Hi All, I have so many picture of my kids, and movies and videos. I really want to create media server. After doing some research on the internet, I am going to install Ubuntu media server. This old server I have has two disk drive. I was thinking about mirroring that. After that I want to... (5 Replies)
Discussion started by: samnyc
5 Replies

6. SCO

SCO OpenServer 5.0.4 Media Needed

Greetings, I've recently been given responsibility for a legacy server running SCO OpenServer 5.0.4 and upon taking inventory I discovered we have all the license documents but no installation media. Can anyone assist me with where I might download these? Thanks Kevin (9 Replies)
Discussion started by: Kevin Harris
9 Replies

7. SCO

Sco media needed for openserver 5.0.6

Hello, i need if possible media for sco openserver 5.0.6 and also want to know if is possible to upgrade from 5.0.2 to 5.0.6. Best regards, Paolo (1 Reply)
Discussion started by: elnino981
1 Replies

8. HP-UX

HP-UX media B.11.11

I need to reinstall The OS on rp3440 system and need HPUX B.11.11 media for risc processor. Can anyone help me? (2 Replies)
Discussion started by: Lapfa01
2 Replies

9. SCO

Need SCO 5.0.6 openserver media kit

hello everyone i need a copy of sco 5.0.6 iso for isntall a new server crash I read in a post that someone uploaded to an ftp an iso but I did not find the ftp any can helpme? (7 Replies)
Discussion started by: mjgeddo
7 Replies

10. SCO

SCO OpenServer 5.0.6 media needed

My media disk is unusable. Can someone provide me an ISO for Openserver 5.0.6? Thank you. Brantley Allen (2 Replies)
Discussion started by: brantleyallen
2 Replies
LURKER-INDEX(1) 					      General Commands Manual						   LURKER-INDEX(1)

NAME
lurker-index -- imports messages into the archive SYNOPSIS
lurker-index [-c <config-file>] [-l <list>] [-i <mbox/maildir>] [-v -d -n -u -f] [-m] DESCRIPTION
lurker-index indexes messages from standard input and stores them in the lurker database. It imports either a single message, or a batch of messages in mbox format. It is important to note that lurker messages in order and may miss new messages delivered during the import. For this reason, you should setup lurker to receive new mail before importing old mail. Only use lurker-index on inactive mail folders! By default, lurker-index reads from standard input in mbox format, delimited by 'From <addr> <date>' lines. Be aware that if the mbox is not delimited correctly between messages it will be interpretted as a single message with an invalid date. To read other sources, see the '-i' option. If input is a single email, use '-m'. OPTIONS
-c config-file Use this config file for lurker settings. -l listid Import messages to the named mailing list. This should match the value in the lurker.conf after the 'list = ' entry. -m Import a single message. In this mode lurker will never interpret 'From ' lines as message delimiters. When being fed newly delivered mail, this is the preferred mode of operation. Try to turn off the 'From ' escaping of your MTA when using this mode, as lurker does it's own escaping which is generally smarter. This option should be used when lurker-index is invoked by the MTA for newly delivered email. -i mbox/maildir Import messages from the specified mailbox or maildir. Lurker-index by default reads a mailbox (mbox format) from standard input. If the '-i' parameter is a file, the file is assumed to be in the mbox format and is read instead of standard input. If the parameter is a directory, the directory is assumed to be in maildir format. If '-m' is used, the input MUST be a raw email, preferably with a mbox header, never a maildir. -v Verbose operation. Lurker will output statistics about import speed to assist you in tweaking options for best throughput on your system. It also helps you know how much longer you will have to wait. -d Drop duplicates per list. This option will check the database to see if the message has already been imported to a mailing list. Only if it has not been imported will lurker append it to the mailbox. Even without this option lurker does not index a message twice. If an import failed part-way through, you probably want this option to avoid needless replication. However, to generate mailboxes which accurately reflect delivery, leave the option off. -n Don't compress messages. This will increase the database size and import speed. Lurker can handle a database with mixed com- pressed and uncompressed messages. However, zcat/gzip and database upgrades cannot. If you need these to function, you should never mix compressed and uncompressed messages within a single mailing list. -u Trust user Date headers from the email more than the delivery time. Normally lurker compares the two and if the user time differs too much from the delivery time, the delivery time is used instead. When this option is used, lurker will simply trust the user Date header whenever it exists, otherwise it uses the delivery time. This option should never be used as a default. It is intended for dealing with corrupt mailboxes or maildirs. A better solution than using this option is to find an uncorrupted copy of the mail. -f Fast import (but vulnerable to power-failure). This may improve the lifetime of your hard-disk and increase import speed by up to 30%. However, if the power fails during import or shortly thereafter, it is possible you will have a corrupted database. If you use a journaling filesystem, lurker guarantees no corruption when you OMIT this parameter. SEE ALSO
lurker-prune(1), lurker-params(1), lurker-list(1), lurker-search(1) lurker documentation on http://lurker.sourceforge.net/ COPYRIGHT
Copyright (C) 2002: Wesley W. Terpstra <terpstra@users.sourceforge.net> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. BUGS
Before reporting a bug, please confirm that the bug you found is still present in the latest official release. If the problem persists, then send mail with instructions describing how to reproduce the bug to <lurker-users@lists.sourceforge.net>. LURKER-INDEX(1)
All times are GMT -4. The time now is 07:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy