49、1. 引言

1. 引言

在当今的商业网络中,提供网络打印服务至关重要。通过使用一些网络连接设备,可以将打印机预算集中在少数高质量设备上,供多个用户共享,而不是购买众多低成本设备。同时,集中放置的打印机更易于维护,也能满足每个人的打印需求。目前,几乎所有主流 Linux 发行版的默认打印服务都是通用 UNIX 打印系统(CUPS)。下面将详细介绍 CUPS 的配置、使用以及如何将 Linux 系统设置为打印服务器。

2. CUPS 服务器的启动

2.1 SystemV 风格启动脚本的系统

对于使用 SystemV 风格启动脚本的 Linux 系统(如许多 Fedora 和 RHEL 版本),启动和关闭 CUPS 打印服务相对简单。可以使用 chkconfig 命令开启 CUPS,使其在每次重启时自动启动,然后运行 cups 启动脚本立即启动 CUPS 服务。在 RHEL 6.x 或更早版本中,以 root 用户身份输入以下命令:

# chkconfig cups on
# service cups start

如果 CUPS 服务已经在运行,应使用 restart 代替 start 。使用 restart 选项也是重新读取 cupsd.conf 文件中可能更改的配置选项的好方法(不过,如果 CUPS 已经在运行, service cups reload 可以在不重启的情

11-21 20:49:50.147 4762 30319 E AndroidRuntime: FATAL EXCEPTION: IpClient.wlan0 11-21 20:49:50.147 4762 30319 E AndroidRuntime: Process: com.android.networkstack.process, PID: 4762 11-21 20:49:50.147 4762 30319 E AndroidRuntime: java.lang.IllegalArgumentException: Wakelock.mLock is already dead. 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3374) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3354) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3337) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3279) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.IPowerManager$Stub$Proxy.acquireWakeLock(IPowerManager.java:1471) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.PowerManager$WakeLock.acquireLocked(PowerManager.java:4194) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.PowerManager$WakeLock.acquire(PowerManager.java:4175) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpReachabilityMonitor$Dependencies$1.acquireWakeLock(IpReachabilityMonitor.java:198) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpReachabilityMonitor.probeAll(IpReachabilityMonitor.java:572) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient.handleUpdateL2Information(IpClient.java:2845) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient.-$$Nest$mhandleUpdateL2Information(IpClient.java:0) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient$StartedState.processMessage(IpClient.java:3388) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:1002) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:820) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:115) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:298) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Looper.loop(Looper.java:408) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:85) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace: 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$WakeLock.linkToDeath(PowerManagerService.java:6302) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$WakeLock.<init>(PowerManagerService.java:6289) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService.acquireWakeLockInternal(PowerManagerService.java:1890) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService.-$$Nest$macquireWakeLockInternal(Unknown Source:0) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$BinderService.acquireWakeLock(PowerManagerService.java:6785) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: 11-21 20:49:50.663 1715 1715 D AndroidRuntime: Shutting down VM 11-21 20:49:50.664 1715 1715 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main 11-21 20:49:50.664 1715 1715 E AndroidRuntime: java.lang.IllegalStateException: Lost network stack. This is not the root cause of any issue, it is a side effect of a crash that happened earlier. Earlier logs should point to the actual issue. 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector.maybeCrashWithTerribleFailure(ConnectivityModuleConnector.java:336) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector.-$$Nest$mmaybeCrashWithTerribleFailure(Unknown Source:0) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector$ModuleServiceConnection.onServiceDisconnected(ConnectivityModuleConnector.java:279) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:2473) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:2488) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:1027) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:108) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:298) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Looper.loop(Looper.java:408) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:1139) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:709) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:613) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1052)
最新发布
11-25
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值