When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
CUPS does take longer than other services but 2 minutes is too long. Does: service cups restart have the same problem. -- ======================================================================= Do you mean that you not only want a wrong answer, but a certain wrong answer? -- Tobaben ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
Name resolution issues? I'd guess that particularly if it's trying to find remote printers on other CUPS servers on your LAN.
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
It sounds like a name resolution is taking a long time. Things to check:
* /etc/hosts
* the ServerName directive in /etc/cups/cupsd.conf -- this defaults to the server's hostname if not present
* does this command take ages too?: host "$(hostname)"
Tim. */
2007/6/26, Tim Waugh twaugh@redhat.com:
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
It sounds like a name resolution is taking a long time. Things to check:
- /etc/hosts
This is my /etc/host file:
# Do not remove the following line, or various programs # that require network functionality will fail. ::1 localhost.localdomain localhost
- the ServerName directive in /etc/cups/cupsd.conf -- this defaults to
the server's hostname if not present
This is my cupsd.conf file # # "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $" # # Sample configuration file for the Common UNIX Printing System (CUPS) # scheduler. See "man cupsd.conf" for a complete description of this # file. #
# Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel info
# Administrator user group... SystemGroup sys root
# Only listen for connections from the local machine. Listen localhost:631 Listen /var/run/cups/cups.sock
# Show shared printers on the local network. Browsing On BrowseOrder allow,deny # (Change '@LOCAL' to 'ALL' if using directed broadcasts from another subnet.) BrowseAllow @LOCAL
# Default authentication type, when authentication is required... DefaultAuthType Basic
# Restrict access to the server... <Location /> Order allow,deny Allow localhost </Location>
# Restrict access to the admin pages... <Location /admin> Encryption Required Order allow,deny Allow localhost </Location>
# Restrict access to configuration files... <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny Allow localhost </Location>
# Set the default printer/job policies... <Policy default> # Job-related operations must be done by the owner or an adminstrator... <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
# All administration operations require an adminstrator to authenticate... <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> AuthType Basic Require user @SYSTEM Order deny,allow </Limit>
# Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
<Limit All> Order deny,allow </Limit> </Policy>
# # End of "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $". #
- does this command take ages too?: host "$(hostname)"
Computer has the name MAXDATA but if I issue $ host maxdata
I get
Host maxdata not found: 3(NXDOMAIN)
while if I issue host localhost I get immediately localhost has address 127.0.0.1
If I restart CUPS service, it restarts in a breeze
Tnx for help
On Wed, 2007-06-27 at 09:18 +0200, antonio montagnani wrote:
Computer has the name MAXDATA but if I issue $ host maxdata
I get
Host maxdata not found: 3(NXDOMAIN)
while if I issue host localhost I get immediately localhost has address 127.0.0.1
I would have expected starting X to be a problem, too, if you were having hostname resolution issues. Things that do reverse lookups, as well, might take even more time than things that don't.
Do you have a local DNS server that resolves names? If so, maxdata should be an entry in the local zone records.
If you're not using one, you can put an entry for maxdata in the /etc/hosts file. If the PC is on a LAN where other computers are networked, then apply it to the LAN address.
e.g. Add a line like the following to the /etc/hosts file, changing the IP address to whatever it is:
192.168.1.1 maxdata
Alternatively, if the machine is only ever used in a stand-alone fashion, you could tag the hostname onto the *end* of the localhost line in the /etc/hosts file.
e.g. 127.0.0.1 localhost.localdomain localhost maxdata
2007/6/27, Tim ignored_mailbox@yahoo.com.au:
On Wed, 2007-06-27 at 09:18 +0200, antonio montagnani wrote:
Computer has the name MAXDATA but if I issue $ host maxdata
I get
Host maxdata not found: 3(NXDOMAIN)
while if I issue host localhost I get immediately localhost has address 127.0.0.1
I would have expected starting X to be a problem, too, if you were having hostname resolution issues. Things that do reverse lookups, as well, might take even more time than things that don't.
Do you have a local DNS server that resolves names? If so, maxdata should be an entry in the local zone records.
If you're not using one, you can put an entry for maxdata in the /etc/hosts file. If the PC is on a LAN where other computers are networked, then apply it to the LAN address.
e.g. Add a line like the following to the /etc/hosts file, changing the IP address to whatever it is:
192.168.1.1 maxdata
Alternatively, if the machine is only ever used in a stand-alone fashion, you could tag the hostname onto the *end* of the localhost line in the /etc/hosts file.
e.g. 127.0.0.1 localhost.localdomain localhost maxdata
-- [tim@bigblack ~]$ rm -rfd /*^H^H^H^H^H^H^H^H^H^Huname -ipr 2.6.21-1.3228.fc7 i686 i386
Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7.
Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
I modified my host file adding a line:
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 maxdata localhost.localdomain localhost ::1 localhost.localdomain localhost
Now the question is: why on system upgrading from FC6 to F7 line was not added, while on fresh installations everything was fine???
And now Cups is not idling any longer...tnx Tim
On Wed, 2007-06-27 at 11:49 +0200, antonio montagnani wrote:
I modified my host file adding a line:
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 maxdata localhost.localdomain localhost ::1 localhost.localdomain localhost
Now the question is: why on system upgrading from FC6 to F7 line was not added, while on fresh installations everything was fine???
Possibly because it's usually best not to change the local loopback lines, if you can help it. You need to be aware of the potential problems, particularly when you try to resolve some problem, later on.
Fresh installs do tend to stick it in there, I've noticed. Thanks to that, I've a few things that think they're "localhost" rather than using a network address that's meaningful to something remote from the box.
On Wednesday 27 June 2007, antonio montagnani wrote:
2007/6/26, Tim Waugh twaugh@redhat.com:
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
When I start my laptop, during booting, when the system arrives at Cups service start-up, it stays idling for one or two minutes - I didn't check with my clock anyway :-) - for sure it is much longer than other services. Where shall I look??
It sounds like a name resolution is taking a long time. Things to check:
- /etc/hosts
This is my /etc/host file:
# Do not remove the following line, or various programs # that require network functionality will fail.
::1 localhost.localdomain localhost
? where is your ipv4 address? Should it also be there? If not, do you have all the ipv6 stuffs enabled?
- the ServerName directive in /etc/cups/cupsd.conf -- this defaults to
the server's hostname if not present
This is my cupsd.conf file # # "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $" # # Sample configuration file for the Common UNIX Printing System (CUPS) # scheduler. See "man cupsd.conf" for a complete description of this # file. #
# Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel info
# Administrator user group... SystemGroup sys root
# Only listen for connections from the local machine. Listen localhost:631 Listen /var/run/cups/cups.sock
# Show shared printers on the local network. Browsing On BrowseOrder allow,deny # (Change '@LOCAL' to 'ALL' if using directed broadcasts from another subnet.) BrowseAllow @LOCAL
# Default authentication type, when authentication is required... DefaultAuthType Basic
# Restrict access to the server...
<Location /> Order allow,deny Allow localhost </Location>
# Restrict access to the admin pages... <Location /admin> Encryption Required Order allow,deny Allow localhost
</Location>
# Restrict access to configuration files... <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny Allow localhost
</Location>
# Set the default printer/job policies...
<Policy default> # Job-related operations must be done by the owner or an adminstrator... <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
# All administration operations require an adminstrator to authenticate... <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> AuthType Basic Require user @SYSTEM Order deny,allow
</Limit>
# Only the owner or an administrator can cancel or authenticate a job...
<Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
<Limit All> Order deny,allow </Limit> </Policy>
# # End of "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $". #
- does this command take ages too?: host "$(hostname)"
Computer has the name MAXDATA but if I issue $ host maxdata
I get
Host maxdata not found: 3(NXDOMAIN)
I believe its case sensitive.
while if I issue host localhost I get immediately localhost has address 127.0.0.1
If I restart CUPS service, it restarts in a breeze
Tnx for help
Antonio Montagnani Skype : antoniomontag
2007/6/27, Gene Heskett gene.heskett@verizon.net:
On Wednesday 27 June 2007, antonio montagnani wrote:
2007/6/26, Tim Waugh twaugh@redhat.com:
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
-- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Gene,
please check my last message, about modified hosts file.
I still do not understand [antonio@MAXDATA ~]$ host maxdata Host maxdata not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$ host MAXDATA Host MAXDATA not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$ host Maxdata Host Maxdata not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$
and my hosts file is:
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 Maxdata localhost.localdomain localhost ::1 localhost.localdomain localhost
Now I do not have any idling on cups at booting stage.
Any clarification???
On Wednesday 27 June 2007, antonio montagnani wrote:
2007/6/27, Gene Heskett gene.heskett@verizon.net:
On Wednesday 27 June 2007, antonio montagnani wrote:
2007/6/26, Tim Waugh twaugh@redhat.com:
On Fri, 2007-06-22 at 13:32 +0200, antonio montagnani wrote:
-- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Gene,
please check my last message, about modified hosts file.
I still do not understand [antonio@MAXDATA ~]$ host maxdata Host maxdata not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$ host MAXDATA Host MAXDATA not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$ host Maxdata Host Maxdata not found: 3(NXDOMAIN) [antonio@MAXDATA ~]$
and my hosts file is:
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 Maxdata localhost.localdomain localhost
This is not ^^^^^^^ exactly kosher, I believe it should be on a separate line that looks something like this, adjust the ipv4 address accordingly though. 192.168.1.2 your-full-domain-name alias alias I don't have any ipv6 stuff setup yet and don't fully understand it, but this line from my hosts file is how I'm doing it.
192.168.71.3 coyote.coyote.den coyote
Because the 192.168 block is NOT allowed past a router, I can use any name as the FQDN of my local network. And your cups.configs can use a syntax such as 192.168.71.3:631 and all the other machines on the local network that have cups configured like that in their cups client.conf files can use this printer as if it was a locally connected printer.
If the client machines also have that line in their hosts file, then they can use syntax such as "coyote:631" in the client.conf files just as easily.
Note that all of this may be rendered obsolete by ipv6, which I haven't attempted to grok yet.
::1 localhost.localdomain localhost
Now I do not have any idling on cups at booting stage.
Any clarification???
Antonio Montagnani Skype : antoniomontag