Sponsored Content
Special Forums IP Networking Remote Printing - UNIX to XP Client Post 302265781 by Ikon on Monday 8th of December 2008 02:02:52 PM
Old 12-08-2008
I know some new Windows service packs have been rolling out. Could have updated something in the firewall.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Remote Printing

I am setting up a unix remote print server for approximately 500 printers. We send about 1,000 print jobs per day over the WAN. I am looking for hardware specs. I know I can overkill, but would rather get a sensible machine. Any suggestions? (2 Replies)
Discussion started by: Donna
2 Replies

2. UNIX for Advanced & Expert Users

Printing Problems in unix ... ( Bar-cdoe - Ip Printing)

Hi guys ... i need ur help with some printing problem in unix ... first prob. : i wanna print from my NCR unix to an Win NT , Ip based printing server ( HP JetDirect ) . My issue , is it possible to print directly to an Ip address from unix ? How do i make it work to get any results ?... (3 Replies)
Discussion started by: QuickSilver
3 Replies

3. UNIX for Dummies Questions & Answers

Remote Printing

I am using Sco Openserver 5.0.6 and I have an Okidata 16n printer on a GETNET print server. I am able to print to the printer. However I am having display issues. Normally when I setup a local printer I am able to tell it what model to use. Ex.(HPLaserJet). When I setup the remote... (2 Replies)
Discussion started by: stufine
2 Replies

4. UNIX for Advanced & Expert Users

Remote printing

I'm trying to print from my Solaris server to a Windows Print Server The Print Server will then pass the print job to a PC connected via dial-up and print it locally. EG: Solaris ----- | | | | ------ /88888/ ------- \ / ... (1 Reply)
Discussion started by: warrickj
1 Replies

5. Solaris

Remote Dial-up Modem Printing With Out Cpu On The Remote Side!

I am looking for a dial-up remote printing solution as under : 1. We have a Centralized location where Sun Solaris (A) is installed. From here printing command will be despatched. 2. This printing command will be routed to WAN cloud to Main Branches (B1,B2,B3)and from there, printer at... (0 Replies)
Discussion started by: jayvee
0 Replies

6. UNIX for Advanced & Expert Users

Remote printing

Dear Sir Please how can I print a job localy with my printer while a server from where I am working belong to another network? Actulally to print a job I am oblige to : 1rst to print it inside a file 2nd coping the file to my network (rcp) 3rt sending the file to my local printer (lp... (2 Replies)
Discussion started by: sobnc
2 Replies

7. SCO

Printing as a CUPS client, only root can print!

Hi, i'm running Openserver 5.0.7 as a CUPS client for a Linux server. The root user can issue a "lpstat -t" to see the printers and can submit jobs without issues. The problem presents when I try to work as a regular user. If I issue an "lpstat -t" all I get after a few seconds is "lpstat:... (1 Reply)
Discussion started by: cyruspy
1 Replies

8. UNIX for Dummies Questions & Answers

Remote Unix printing to my WinXP works with no router. How can I make it work through my router?

I set up remote printing on a clients Unix server to my Windows XP USB printer. My USB printer is connected directly to my PC (no print server and no network input on printer). With my Win XP PC connected to my cable modem (without the router), i can do lp -dhp842c /etc/hosts and it prints. I... (7 Replies)
Discussion started by: jmhohne
7 Replies

9. SCO

Unix remote printing

Sir, i have a sco 5.5 installed server and 6 clients connected through pci specialix card and printing working fine in these all terminals. 7 and 8 ports are free now, i need to setup another terminal for login on through 7 or 8 port for remote login. i connect a external modem using 25 pin male... (2 Replies)
Discussion started by: Aneesh Kumar.T
2 Replies

10. UNIX for Dummies Questions & Answers

Sco Unix printing : jobs hangs in queue - printing via lp versus hpnpf

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts). This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies
appender_type_rollingfile.h(3)					       log4c					    appender_type_rollingfile.h(3)

NAME
appender_type_rollingfile.h - Log4c rolling file appender interface. SYNOPSIS
#include <log4c/defs.h> #include <log4c/appender.h> #include <log4c/rollingpolicy.h> Functions LOG4C_API rollingfile_udata_t * rollingfile_make_udata (void) LOG4C_API int rollingfile_udata_set_logdir (rollingfile_udata_t *rfudatap, char *logdir) LOG4C_API int rollingfile_udata_set_files_prefix (rollingfile_udata_t *rfudatap, char *prefix) LOG4C_API int rollingfile_udata_set_policy (rollingfile_udata_t *rfudatap, log4c_rollingpolicy_t *policyp) LOG4C_API const char * rollingfile_udata_get_logdir (rollingfile_udata_t *rfudatap) LOG4C_API const char * rollingfile_udata_get_files_prefix (rollingfile_udata_t *rfudatap) LOG4C_API long rollingfile_get_current_file_size (rollingfile_udata_t *rfudatap) Variables __LOG4C_BEGIN_DECLS LOG4C_API const log4c_appender_type_t log4c_appender_type_rollingfile Detailed Description Log4c rolling file appender interface. The rolling file appender implements a logging mechanism of a list of files up to a maximum number. The files are written by default to the current directory with logging names folowing the pattern log.1, log.2 etc. These parameters may be changed using the appropriate setter functions. If the appender fails to open logfiles for writing then the messages are logged to stderr--it will continue to try to open the zero-th file for writing at rollover events so if it succeeds at some point to open that file the messages will start to appear therein and will no longer be sent to stderr. Switching from logging from one file to the next is referred to as a 'rollover event'. The policy that determines when a rollover event should happen is called a 'rolling policy'. A mechanism is provided to allow different rolling policies to be defined. Log4c ships with (and defaults to) the classic size-window rollover policy: this triggers rollover when files reach a maximum size. The first file in the list is always the current file; when a rollover event occurs files are shifted up by one position in the list--if the number of files in the list has already reached the max then the oldest file is rotated out of the window. See the documentation in the rollingpolicy_type_sizewin.h file for more details on the size-win rollover policy. Function Documentation LOG4C_API long rollingfile_get_current_file_size (rollingfile_udata_t *rfudatap) Get the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the current size of the file being logged to. LOG4C_API rollingfile_udata_t* rollingfile_make_udata (void) Get a new rolling file appender configuration object. Returns: a new rolling file appender configuration object, otherwise NULL. LOG4C_API const char* rollingfile_udata_get_files_prefix (rollingfile_udata_t *rfudatap) Get the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the prefix. LOG4C_API const char* rollingfile_udata_get_logdir (rollingfile_udata_t *rfudatap) Get the logging directory in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. Returns: the logging directory. LOG4C_API int rollingfile_udata_set_files_prefix (rollingfile_udata_t *rfudatap, char *prefix) Set the prefix string in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. prefix the logging files prfix to use. Returns: zero if successful, non-zero otherwise. LOG4C_API int rollingfile_udata_set_logdir (rollingfile_udata_t *rfudatap, char *logdir) Set the logging directory in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. logdir the logging directory to set. Returns: zero if successful, non-zero otherwise. LOG4C_API int rollingfile_udata_set_policy (rollingfile_udata_t *rfudatap, log4c_rollingpolicy_t *policyp) Set the rolling policy in this rolling file appender configuration. Parameters: rfudatap the rolling file appender configuration object. policyp the logging files prfix to use. Returns: zero if successful, non-zero otherwise. Variable Documentation __LOG4C_BEGIN_DECLS LOG4C_API const log4c_appender_type_t log4c_appender_type_rollingfile rollingfile appender type definition. This should be used as a parameter to the log4c_appender_set_type() routine to set the type of the appender. Author Generated automatically by Doxygen for log4c from the source code. Version 1.2.1 Mon May 2 2011 appender_type_rollingfile.h(3)
All times are GMT -4. The time now is 05:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy