Re: Invalid Argument?

"Brian Lalor" <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <[email protected]>
On 1 Feb 2002, Hunter Matthews wrote:

> Wha? 'r' is the read-only mode for bsddb. 
> 
> Would you post your config file? Leave out your server secret.

Attached.  Anything else that would help, like version numbers of 
packages, etc?

--
Brian Lalor
[email protected]
current.conf (text/plain, 4.8 KB)
# current config file
# 
# Don't blame me for the format: I'm using as many standard python modules
#   as possible
#

# General guidelines:
# 1. Every current.conf must have a "current" section, which is the 
#    main config section.
# 2. Section name rule -> '-', '_', alphanum
# 3. field name rule  -> '-', '.', '_', alphanum
# 4. All fields must be present, even if blank.
# 

# General Section descriptions:
# [current]
# valid_channels = list of all the channels to actually use. This allows 
#                  the admin to define a channel for future use, or disable
#                  an old channel without deleting anything.
# log_file = File to send log messages to
# log_level = How much should we send to the log file?
# port_number = what port number should the server be listening on?
#
#
# [channel-section]
# label = Text identifier for this channel. Used as a text index.
#         Values are "redhat-linux-i386-7.1" or "redhat-rawhide-i386"
#         Not the same as the channel section name because labels need '.'
# name = Text name (human readable) name of this distribution
#        Should be only 1 line.
# parent_channel = Channel representing the base channel that provides most
#                  of the packages to this one, blank otherwise.
# arch = The cannonical architecture (a family of archs that this
#        channel supports. (i386, sparc, alpha. Not i686, etc)
# os_release = Release of the channel. 6.2, 7.0, 7.2, whatever.
# description = Textual description of what the channel represents. This 
#               can be blank or a short paragraph.
# rpm_dirs = list of all the dirs that contain binary rpms that should be
#            served to clients
# src_dirs = similarly, list of all the src rpms that should be served.
#            Can be empty, but not missing (currently)
# db_dir   = directory containing the current databases
# 
# Note that all channels will also have a "last_modified" field, which will
# will automatically be created/updated.

[current]
valid_channels = insight-i386-6.2
#log_file = ./current.log    
#pid_file = ./current.pid
log_level = 1
http_port = 8080
https_port = 8081
server_id = purple
#key_file = ./current.pem

# These are some text messages that the server can return to the clients
#  in various API calls.
## FIXME: ConfigParser just keeps getting more and more broken by this
## stuff. The period is there ot provide a "blank line". Sheesh.
welcome_message = "Welcome to blalor's up2date server."
privacy_statement = "Privacy Statement for Hunter's up2date server: 
    This is the internet - privacy is an illusion. 
    .
    Please note that only anonymous access is supported anyway - so while you 
    have to get a valid system id (by going through the rhn_register program) 
    there is no requirement to fill those fields out with real data. :) All 
    that is required is that your architecture an os_release be accurately 
    reported - and rhn_register fills that in automatically. "

[insight62]
label = insight-i386-6.2
name = Insight 6.2
parent_channel = 
arch = i386
os_release = 6.2
description = Insight 6.2 is Red Hat Linux 6.2 with all the errata
              applied, plus some Duke specific packages.

rpm_dirs = /home/blalor/ftp/devbox/current

# xrpm_dirs = /local/scratch/dulug-7.1/i386/other-pkgs/rawhide

src_dirs =  
db_dir = /usr/local/scratch/insight-6.2/i386/current

# Note: since they are NOT included in valid_channels above, these channels
# won't be created or used. They are just "live" doc.

# The following is an example of what a sub-channel might look like.
# It might be better to leave arch and os_release out of sub-channels, as 
#   they'll have to have the same values as the parent anyway.
[bio71]
label = biology-7.1
name = Duke Biology 7.1
parent_channel = dulug-i386-7.1
arch = i386
os_release = 7.1
description = Duke Biology specific package will build upon Dulug 7.1

rpm_dirs = /local/scratch/dulug-7.1/i386/other-pkgs/bio
src_dirs = 
db_dir = /local/scratch/dulug-7.1/i386/current/bio


[redhat62]
label = redhat-linux-i386-6.2
name = Red Hat Linux i386 6.2
parent_channel = 
arch = i386
os_release = 6.2
description = Red Hat i386 6.2, with all errata applied.

rpm_dirs = /local/scratch/redhat-6.2/i386/RedHat/RPMS
           /local/scratch/redhat-6.2/i386/other-pkgs/dukebio
           /local/scratch/redhat-6.2/i386/other-pkgs/dulug
           /local/scratch/redhat-6.2/i386/other-pkgs/helix
           /local/scratch/redhat-6.2/i386/other-pkgs/misc
           /local/scratch/redhat-6.2/i386/other-pkgs/powertools
           /local/scratch/redhat-6.2/i386/other-pkgs/powertools-updates
           /local/scratch/redhat-6.2/i386/other-pkgs/rh-updates
src_dirs = 
db_dir = /local/scratch/redhat-6.2/i386/current


## END OF LINE ##
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.