GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  POPULAR-LOG (7)

NAME

popular-log - log messages from POPular programs

CONTENTS

DESCRIPTION

This is a list of all the log messages printed by pcheckd(8), pproxy(8), pserv(8), and pdeliver(8) .

LOG LEVEL

DBG debug messages 
INF informational messages 
ERR error messages 
ADM admin intervention required 
SOS critical event 
BUG software bug 

MESSAGE LIST

IDLvl Name
Description
0001INF start
Pserv has started. The server is mostly initialized.
0004BUG left_main_loop
Somehow the main loop was terminated. This should never happen.
0005INF shutdown_server
The pserv server is shut down.
0006ADM dir_access_failed
The opendir() system call on a mailbox directory failed. This probably means that something is wrong with permissions in the pop spool.
0007SOS out_of_memory
Pserv couldn’t allocate memory to hold a mail message structure.
0008ADM name_too_long
The name of a mailbox directory and file is too long.
0009ADM stat_failed
The stat() system call failed for a mail message file. The message will not be listed. This should never happen and probably means that somebody tinkered around with a mailbox file by hand and got the permission wrong.
000aINF log_reopen
The logfile will be reopened now. This should be the last message of the parent process of the server to the log file. (See 000c for the message in the new log file)
000bSOS log_reopen_failed
Reopening of the log file failed for some reason. The old file will be kept open.
000cINF log_reopened
0014SOS out_of_memory
Pserv can’t allocate memory for a msglist structure.
0018ERR unknown_command
The client sent an unknown POP command.
0019SOS no_session_found
The pserv parent process got a process id from wait() that he doesn’t know about, i.e. that shouldn’t be one of his children. This should never happen and probably means that there is some serious data corruption or a bug in the program. pserv will immediately exit.
0020ADM child_died
A child of pserv or pproxy died with non-zero exit code. See the log entries of the child for more details about what happend.
0021SOS child_died_signal
A child of pserv or pproxy died because of a signal. This can either mean that there is a bug in the program of the system has big problems (like running out of memory).
0022SOS out_of_memory
There is no memory to allocate an io context struct. The program is immediately terminated.
0023ERR getpeername_failed
The getpeername() call failed. This probably means that the client and subsequently the proxy has closed the connection.
0024ADM mailbox_too_long
The mailbox name that the proxy sent to the pserv is too long.
0025ADM mailbox_too_long
The mailbox name that the proxy sent to the pserv is too long.
0026ADM bad_mailbox
The mailbox name that the proxy sent to the pserv has a leading ’/’.
0027ADM bad_mailbox
The mailbox name that the proxy sent to the pserv has funny chars in it. Only the following chars are allowed: a-z, A-Z, 0-9, allowed.
0028ADM id_too_long
The id that the proxy sent to the pserv is too long.
0029ADM id_too_long
The id that the proxy sent to the pserv is too long.
0030ADM bad_id
The id that the proxy sent to the pserv has funny chars in it. Only the following chars are allowed: a-z, A-Z, 0-9, ’.’, ’_’, ’-’.
0031ADM flags_too_long
The flags that the proxy sent to the pserv are too long.
0032ADM flags_too_long
The flags that the proxy sent to the pserv are too long.
0033ADM bad_flags
The flags that the proxy sent to the pserv have funny chars in it. Only a-z, A-Z, 0-9 are allowed.
0034INF login
A new connection from the proxy is coming in and the mailbox name, the logging id and the flags have been received.
0035ADM null_byte_in_input
A null byte was encountered in input from a network socket. This can never happen in a normal POP3 connection.
0037ADM msg_unlink_failed
After the QUIT command has been received, the server tried to delete a message but failed.
0038ADM msg_rename_failed
After the QUIT command has been received, the server tried to rename a message from the ’new’ into the ’cur’ directory but failed.
0039INF quit
This message is logged after the client send a QUIT. It contains statistics about the number of mails in mailbox, the number of new mails, the number of read mails, and the number of deleted mails.
003aSOS socket_call_failed
When trying to open a listening socket, the socket system call failed.
003bSOS setsockopt_failed
When trying to open a listening socket, the setsockopt call to set SO_REUSEADDR failed.
003cSOS bind_failed
When trying to open a listening socket, the bind() failed.
003dSOS listen_failed
When trying to open a listening socket, the listen() failed.
003eERR accept_error
The accept() call failed. This probably means that the client closed the connection before the server could accept it. If this occures only occasionally, it is harmless. If it occures more often, it might indicate network problems.
003fSOS fork_failed
Pserv tried to fork a child and that failed. This probably means that the system is overloaded. The connection to the client will be closed and we try to keep going.
0042SOS select_error
The select () syscall in the main loop returned an error that is not handled. This should never happen.
0047ERR unknown_command
An unknown POP3 command was received from the client. The client got an error message. No action needs to be taken.
0048ERR user_name_too_long
The user name that the client sent is too long for some internal buffer. The buffer should be big enough for any sensible name.
0049ERR write_error
An error occurred while writing to the client. This probably means that the client closed the connection.
004aERR unknown_command
An unknown POP3 command was received from the client. The client got an error message. No action needs to be taken.
004bERR password_too_long
The password that the client sent is too long for some internal buffer. The buffer should be big enough for any sensible password.
004cADM pdm_reload_failed
The reloading of a pdm module failed because this module doesn’t support the pdm_reload() function.
004dSOS pdm_error
A module returned an internal error while checking a user. This means that the module is confused, maybe the underlain database is corrupted. Check for log messages from the module itself to find out more.
004eSOS pdm_error
A module returned an internal error while checking a user. This means that the module is confused, maybe the underlain database is corrupted. Check for log messages from the module itself to find out more.
004fERR readln_timeout
A timeout occurred while waiting for an input line from a socket. This probably means that the client went away.
0050ERR readln_error
An error occurred while waiting for an input line from a socket. This probably means that the client went away.
0051ERR readln_eof
An end-of-file occurred while waiting for an input line from a socket. This probably means that the client went away.
0052ERR readln_too_long
A line was read that is too long. This might indicate an attack. The buffer is long enough for any reasonable POP3 command etc.
0053ADM stat_failed
The stat() of a mail message file failed. A size of 0 will be used. The quota can’t be calculated accurately.
0054ADM rename_failed
After the mail message has been written to the ’tmp’ directory, it can’t be renamed to the ’new’ directory.
0055INF delivered
A mail has been delivered successfully.
0056ADM opendir_failed
The opendir() system call failed while trying to determine the mailbox size.
0057ERR quota_exceeded
The quota on a mailbox was exceeded. No mail will be delivered.
0058ERR quota_exceeded
The quota on a mailbox was exceeded. No mail will be delivered.
0059SOS mailboxdir_error
Pdeliver can’t change into the mailbox directory.
005aADM open_tmpfile_failed
Opening the tmp file for a new mail message failed.
005bADM fdopen_failed
fdopen() on new tmp file for mail message failed.
005cADM write_mail_failed
A write to the tmp file for a new mail message failed.
005dADM close_failed
The close on the tmp file for a new mail message failed.
005eINF debug_type
The debug options were changed through pcontrol. These are the new options that are used from now on.
005fINF shutdown_all_received
The command ’shutdown all’ was received from pcontrol. The server will shut down all it’s children and the exit itself.
0060INF shutdown_parent_received
The command ’shutdown parent’ was received from pcontrol. The server will shut down itself, but not its children.
0061ADM pcontrol_recvfrom_failed
The call to recvfrom() to get a command from pcontrol failed.
0062ADM pcontrol_sendto_failed
The call to sendto() to send an answer to pcontrol failed.
0063ADM no_mailbox
Changing into mailbox directory failed.
0064ADM mkdir_failed
Creation of the mailbox directory failed.
0065ADM no_mailbox
Changing into mailbox directory failed.
0066ADM mkdir_failed
Creation of the ’new’ directory failed.
0067ADM mkdir_failed
Creation of the ’cur’ directory failed.
0068ADM mkdir_failed
Creation of the ’tmp’ directory failed.
0069INF checking
Checking user in POPular database modules.
006aINF result_user_accepted
The user was accepted by a pdm module.
006bINF result_user_exists
The user was found by a pdm module but authentication failed.
006cINF result_pdm_internal_error
A pdm module returned an internal error.
006dINF result_unknown_user
The user was not found by any pdm module.
006eINF result_unknown_result_code
An unknown result code was returned by pdm_auth_user().
006fADM unknown_protocol
An unknown protocol identifier was used in the command file. The program is terminated.
0070INF start
Pcheckd has been started and partially initialized.
0072ADM invalid_mailbox
The mailbox name that the client sent is invalid. The name is not allowed to start with a ’/’
0073ERR opendir_failed
The ’new’ directory for the given mailbox can’t be opened. This probably means that the mailbox hasn’t been created yet.
0074ADM opendir_failed
The ’cur’ directory for the given mailbox can’t be opened.
0075ADM unknown_request
The client sent an unknown request. Allowed are ’L’ for load check and ’M’ for mailbox check.
0076ERR sendto_failed
Sending the answer of the requested check back to the client failed.
0077SOS select_error
The select () syscall in the main loop returned an error that is not handled. This should never happen.
0078INF shutdown
pcheckd received a QUIT, INT, TER, or PWR signal and is shutting down.
0079INF debug_disabled
pcheckd received a SIGUSR1 and disabled debuglogging.
007aINF debug_enabled
pcheckd received a SIGUSR2 and enabled debuglogging.
007cSOS no_session_found
The pproxy parent process got a process id from wait() that he doesn’t know about, i.e. that shouldn’t be one of his children. This should never happen and probably means that there is some serious data corruption or a bug in the program. pproxy will immediately exit.
007dINF shutdown_server
The pproxy server is shut down.
0084INF open_port
Pproxy has been instructed to listen to a new IP number and port.
0085SOS port_open_send_failed
Sending a port open request to the ringd process failed.
0086SOS port_open_failed
Opening of the port failed for some reason on the pproxy side.
0087SOS listen_failed
The listen() system call on the just opened and bound socket failed.
0089SOS fork_failed
Pproxy tried to fork a child and that failed. This probably means that the system is overloaded. The connection to the client will be closed and we try to keep going.
008aINF start
PProxy has started and is mostly initialized.
008dADM pidfile_symlink_failed
The symlink to the pidfile failed. The server will continue to run.
008eSOS select_error
The select () syscall in the main loop returned an error that is not handled. This should never happen.
008fBUG left_main_loop
Somehow the main loop was terminated. This should never happen.
0096SOS backend_socket_call_failed
Creating a socket for a connection to the backend failed.
0097SOS connect_to_backend_failed
The connect to a backend failed.
0098SOS backend_read_err
A read from a POP3 backend failed.
0099SOS backend_not_ready
A POP3 backend sent a -ERR reply on connection.
009aSOS backend_read_err
A write to a POP3 backend failed.
009bSOS backend_read_err
A read from a POP3 backend failed.
009cADM login_failed
The login to a POP3 backend server failed. The answer to the USER command was -ERR.
009dSOS backend_read_err
A write to a POP3 backend failed.
009eSOS backend_read_err
A read from a POP3 backend failed.
009fADM login_failed
The login to a POP3 backend server failed. The answer to the PASS command was -ERR.
0100SOS socket_call_failed
The creation of a UDP socket to talk to the pcheckd on a backend failed.
0101SOS connect_failed
The connect() call on the UDP socket to the pcheckd on a backend failed.
0102SOS buffer_to_small
A buffer for sending a mailbox name to the pcheckd is too small.
0103SOS send_failed
The send() call sending a request to the pcheckd failed.
0104SOS select_failed
The select () call waiting for answer from pcheckd failed in an unexpected way.
0105SOS recv_failed
Recv() call failed when reading answer from pcheckd.
0106ERR check_udp_timeout
Pproxy timed out waiting for an answer from pcheckd.
0107ERR timeout
A timeout occurred while proxying data.
0108INF quit
The proxy child shuts down after its work is done. The proxied bytes in both directions are reported.
0109INF quit
The client closed the connection while faking a POP3 dialog.
010aINF quit
The client send a quit while faking a POP3 dialog.
010cSOS out_of_memory
There is not enought memory to allocate an IO context.
010dSOS write_to_backend_failed
A write call to the backend failed.
010fSOS out_of_memory
There is not enought memory to allocate an IO context.
0110BUG illegal_value
The do_pop3_auth() function returned an illegal value.
0111ERR getsockname_error
getsockname() returned an error. This probably means that the client disconnected before we could look at the socket.
0112ERR getpeername_error
getpeername() returned an error. This probably means that the client disconnected before we could look at the socket.
0113INF connect
Incoming connection from client.
0114BUG unknown_protocol
No protocol information for this virtual server is found. This should never happen.
0116SOS out_of_memory
There is not enought memory to allocate an IO context.
0117INF virt_serv_disabled
The virtual server is disabled
0118ERR write_error
A write to the client failed.
0119ERR write_error
A write to the client failed.
011bERR quit
Client sent QUIT command in authentication phase.
011cINF virt_serv_fake
The virtual server is to be faked.
011dERR auth_fail
The authorisation of the user failed because of the client IP number.
011eERR auth_fail
The authorisation of the user failed because of the protocol used.
011fERR auth_fail
The authorisation of the user failed because the wrong password was given.
0120ERR auth_fail
The authorisation of the user failed for unknown reasons.
0121BUG illegal_auth_result
A PDM module returned an illegal result code.
0122SOS unknown_backend
A PDM module told us which backend to use. Unfortunately this backend is not configured.
0123INF user_auth
User was authenticated.
0124INF operation
The backend is configured to be faked.
0125INF quit
The backend is configured to be offline.
0126INF operation
The backend uses POP3 protocol. Proxying will now be started.
0127INF operation
The backend pcheckd told us that the mailbox is empty, the load on the storage server is too high, or the maximum number of sessions is reached on the storage server or a timeout occured while waiting for the answer from the pcheckd. The POP connection will be faked locally.
0128INF operation
The backend uses XPOP protocol. Proxying will now be started.
0129BUG invalid_value
Invalid value for the backend protocol.
012aBUG invalid_value
Invalid value for the backend state.
012bINF shutdown_children_received
The command ’shutdown children’ was received from pcontrol. The server will shut down all it’s children.
012cINF shutdown_children
The pproxy server is shutting down all its children.
012dINF shutdown_children
The pserv server is shutting down all its children.
012eINF shutdown_delayed
The pproxy server closed all listening ports. After all children have died, it will close down.
012fINF shutdown_delayed_received
The command ’shutdown delayed’ was received from pcontrol. The server will not accept new connections and shut down itself after the last child has died.
0130INF all_children_gone
All children have died and the server got a delayed shutdown command earlier. It will shutdown now.
0131INF all_children_gone
All children have died and the server got a delayed shutdown command earlier. It will shutdown now.
0132INF shutdown_delayed
The pserv server closed the listening ports. After all children have died, it will close down.
0133INF got_term_signal
The child got a TERM or INT signal and will shut down. This signal was either delivered to the parent between the last check for signals and the fork, or it was delivered to the child before the child could change its signal handling to the default behaviour. In any case, calling exit immediately is the right thing to do here.
0135SOS open_statefile
Open of the state file failed. The program will be terminated.
0136SOS seek_statefile
Seeking inside the state file failed. The program will be terminated. Try deleting the state file before restarting.
0137SOS write_statefile
Writing to state file failed. The program will be terminated. Try deleting the state file before restarting.
0138SOS mmap_statefile
Mmapping the state file failed. The program will be terminated. Try deleting the state file before restarting.
0139ADM symlink_statefile_failed
The symlinking of the real state file to its symbolical name failed. The server will still work, but the pstatus program will not find the state file.
013aSOS control_socket_open_failed
Opening of the UNIX domain control socket failed. The program will be terminated.
013bSOS control_bind_failed
Binding the UNIX domain control socket failed. The program will be terminated.
013cSOS control_symlink_failed
Linking the UNIX domain control socket to the canonical name failed. The programm will be terminated.
0140ADM pidfile_open_failed
The opening of the pidfile failed. The server will continue to run.
0141ADM unlink_file_in_rundir_failed
An unlink() operation in the run directory failed. The file can be a pid file, the state file or the control socket.
0142ADM unlink_link_in_rundir_failed
An unlink() operation in the run directory failed. The filename is a link to either a pid file, a state file or a control socket.
0143SOS port_open_no_fd
The opening and binding of the port by the ringd process failed for some reason. The message from the ringd process is printed with this message.
0144INF stat
Statistics from pcheckd: ’requests’ is the number of all requests that pcheckd got, ’mailchecks’ is the number of new format mailcheck requests, ’mailchecks_old’ the number of old format mailcheck requests, ’empty’ the number of requests finding an empty mailbox, ’not_empty’ the number of requests finding a not empty mailbox, ’load_too_high’ the number of requests answered with that message, and maximum number of pserv sessions was used. The statistics are logged and cleared on SIGHUP.
0145SOS select_error
An error occurred in the select () system call while proxying data.
0146ERR accept_failed
The accept () system call failed for some reason.
0147ERR msg_rename_failed
Renaming of a mail file failed, because it is not there. Another pserv process probably got to this file before we did.
0148ERR msg_unlink_failed
Deleting of a mail message failed. Probably another pserv process was faster.
0149ADM config_set
A config variable was set to a new value.
014aBUG sigaction_failed
A sigaction () system call failed. This should never happen.
014bADM config_set
A config variable was set to a new value.
014dADM config_set
A config variable was set to a new value.
014eADM server_now_online
The server listens on a port now and accepts connections. You should see this log message in response to a ’server online’ command.
014fADM server_now_offline
The server closed its listening port and doesn’t accept any new connections. You should see this log message in response to a ’server offline’ command.
0150ADM config_capa
Capability was configured
0151ADM config_capa
Capability was configured
0152ADM config_capa
Capability was configured
0153ADM config_capa
Capability was configured
0154ADM bad_mailbox
The mailbox name that the proxy sent to the pserv has funny chars in it. Only the following chars are allowed: a-z, A-Z, 0-9, allowed.
0155SOS fork_failed
The fork () system call in pcheckd failed.
0156ADM child_died
A child of pcheckd died with non-zero exit code. See the log entries of the child for more details about what happened.
0157ADM child_died_signal
A child of pcheckd died because of a signal. This can either mean that there is a bug in the program of the system has big problems (like running out of memory).
0158ERR mailfile_does_not_exist
A mail message file does not exist. This probably means that the mail has been deleted by another POP session running at the same time.
0159ADM mailfile_open_failed
Opening a mail message file for reading failed.
015aSOS mailfile_mmap_failed
The mmap () system call on the mail message file failed.
015bSOS mailfile_munmap_failed
The unmap () system call on the mail message file failed.
015dERR write_error
Error writing mail message to proxy socket.
015eERR write_error
Error writing mail message to proxy socket.
015fERR write_error
Error writing mail message to proxy socket.
0160ADM config_set
A boolean config variable was set to a new value. (0=no=off=false, 1=yes=on=true)
0161ERR write_error
Error writing mail message to proxy socket.
0162ADM msg_size_zero
A mail message has size zero. It will not be listed.
0163ADM config_backend_del
A ’backend del’ command was executed.
0164ADM config_backend_flush
A ’backend flush’ command was executed.
0165ADM config_backend_conf
A ’backend conf’ command was executed.
0166ADM config_vserv_conf
A ’vserv conf’ command was executed.
0167ADM config_vserv_flush
A ’vserv flush’ command was executed.
0168ADM config_vserv_del
A ’vserv del’ command was executed.
0169ADM config_capa_load
A ’capa load’ command was executed.
016aADM config_capa_del
A ’capa del’ command was executed.
016bADM config_pdm_add
A ’pdm add’ command was executed.
016cADM config_pdm_del
A ’pdm del’ command was executed.
016dADM config_pdm_reload
A ’pdm reload’ command was executed.
016eADM config_pdm_flush
A ’pdm flush’ command was executed.
016fBUG illegal_session_state
The state in sess_ok() has an illegal value. This can never happen. The server keeps going but might log strange things.
0170ADM session_state
The session state is printed. This can be one of ’OK’, ’WARN’, ’MAX’. See the documentation for the exact meaning of these messages.
0171BUG illegal_load_state
The state in sess_load() has an illegal value. This can never happen. The server keeps going but might log strange things.
0172ADM load_state
The load state is printed. This can be one of ’OK’, ’WARN’, ’MAX’. See the documentation for the exact meaning of these messages.
0173SOS touch_failed
Creating or ’touching’ of a flag file failed.
0174SOS unlink_failed
Unlink of a flag file failed.
0177ERR auth_fail
The authorisation of the user failed because the user is unknown.
0178ADM select_error
The rel_select() call failed.
0179INF operation
The backend uses XPOP protocol. Proxying will now be started.
017aADM config_set
A config variable was set to a new value.
017cERR child_died_timeout
A child of pserv or pproxy died because of an ALRM signal. This means that ’sessiontimeout’ (or, for pproxy, ’authtimeout’) ran out.
017dINF msg_info
A message was deleted.
017eINF msg_info
A message was moved from new to cur.
017fERR too_many_bad_commands
Too many bad commands were received while in auth phase. The server will close the connection. The number is configured in the MAX_BAD_COMMANDS define in pconfig.h
0180ERR too_many_bad_commands
Too many bad commands were received while in auth phase. The server will close the connection. The number is configured in the MAX_BAD_COMMANDS define in pconfig.h
0181SOS sock_open_failed
Pproxy tried to open a unix domain socket to talk to the ringd and this failed
0182SOS sock_connect_failed
Pproxy tried to connect to the unix domain socket of the ringd and this failed
0183INF start
ringd has started.
0184SOS open_socket
ringd can’t open the unix domain socket to listen for commands.
0185SOS chown_socket
ringd can’t chown its unix domain socket.
0186INF quit
ringd go a signal and will quit now.
0187SOS socket_max_reached
The maximum number of sockets is reached. If you need more sockets change RINGD_MAX_SOCK and recompile.
0188ADM socket_error
The socket system call returned an error.
0189ADM setsockopt_error
The setsockopt system call returned an error.
018aSOS bind_error
The bind system call returned an error.
018bINF port_list
List of currently opend ports.
018cADM unknown_command
ringd received an unknown command.
018dADM space_char_missing
ringd misses the space char at the 2nd position in the command string which separates the command from arguments.
018eADM space_char_missing
ringd misses the space char in the command string which separates the first from the second argument
018fADM port_invalid
The port number given as second argument to a ringd command is syntactically invalid.
0190ADM port_out_of_range
The port number given as second argument to a ringd command is out of range.
0191ADM port_forbidden
The port number given as second argument to a ringd command is forbidden by configuration (change ALLOWED_PORTS and recompile).
0192ADM invalid_ip
The port number given as first argument to a ringd command is is invalid.
0193INF close_port
Pproxy has been instructed to listen to a new IP number and port.
0194SOS port_close_send_failed
Sending a port close request to the ringd process failed.
0195SOS port_close_failed
Closing of the port failed for some reason on the pproxy side.
0196SOS server_method_failed
A SSL*_server_method() call failed. This probably means that there is something wrong with your openssl library setup.
0199ERR tls_init_failed
Initialization of new TLS connection failed (SSL_new call failed).
019aERR tls_set_fd_failed
Initialization of new TLS connection failed (SSL_set_fd call failed).
019bERR tls_accept
Initialization of new TLS connection failed (SSL_accept call failed).
019cBUG unknown_protocol
No protocol information for this virtual server is found. This should never happen.
019dADM key_file_error
The TLS key file could not be opened. (Call to SSL_CTX_use_RSAPrivateKey_file failed.)
019eADM certificate_file_error
The TLS key file could not be opened. (Call to SSL_CTX_use_RSAPrivateKey_file failed.)
019fERR tls_init_after_stls_failed
Initialization of new TLS connection after STLS failed. The connection will be dropped because we can’t do anything else at this point. The +OK was already sent because we had to send it before initializing TLS on this socket.
0200INF switch_to_tls
Connection is switched to TLS after STLS command.
0201INF switch_to_tls
Connection is switched to TLS after STLS command.
0202ERR tls_init_after_stls_failed
Initialization of new TLS connection after STLS failed. The connection will be dropped because we can’t do anything else at this point. The +OK was already sent because we had to send it before initializing TLS on this socket.
0203SOS tls_seed_failed
Initialization of the TLS pseudo random number generator failed. This is serious because it could potentially mean that there is no security at all.

FILES

/var/log/popular/pcheckd Log file of the pcheckd(8) program
/var/log/popular/pproxy Log file of the pproxy(8) program
/var/log/popular/pserv Log file of the pserv(8) program
/var/log/popular/pdeliver Log file of the pdeliver(1) program

SEE ALSO

pcheckd(8), pdeliver(1), pproxy(8), pserv(8), The POPular Manual

AUTHOR

Jochen Topf jochen@remote.org

http://www.remote.org/jochen/mail/popular/ <URL:http://www.remote.org/jochen/mail/popular/>

COPYRIGHT

The POPular suite is copyright (C) 1999-2002 by Jochen Topf jochen@remote.org.

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; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY 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

Search for    or go to Top of page |  Section 7 |  Main Index


POPULAR-LOG (7)

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.