系统重启原因总结

最新推荐文章于 2021-08-01 01:47:49 发布
置顶 最新推荐文章于 2021-08-01 01:47:49 发布
阅读量5.1k 收藏
点赞数 1
分类专栏： 原理 配置 应用 程序
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/syh63053767/article/details/8885731
版权
应用 同时被 3 个专栏收录
156 篇文章 0 订阅
订阅专栏
程序
99 篇文章 0 订阅
订阅专栏
原理
80 篇文章 0 订阅
订阅专栏

原因二：未发生段错误,SD卡强行Kill掉sysem_server中的许多服务，导致系统重启

Line 116654: 04-19 10:37:21.967   124   545 E ProcessKiller: Process /system/bin/mediaserver (145) has open file /mnt/secure/staging/录音/.上午 10时37分 .ogg
Line 116655: 04-19 10:37:21.968   124   545 E ProcessKiller: Sending SIGKILL to process 145

Line 116656: 04-19 10:37:21.988   123   123 I ServiceManager: service 'media.audio_policy' died
 Line 116657: 04-19 10:37:21.988   123   123 I ServiceManager: service 'media.audio_flinger' died
 Line 116658: 04-19 10:37:21.988   123   123 I ServiceManager: service 'media.player' died
 Line 116659: 04-19 10:37:21.988   123   123 I ServiceManager: service 'memory.dumper' died
 Line 116660: 04-19 10:37:21.988   123   123 I ServiceManager: service 'media.camera' died
 Line 116662: 04-19 10:37:21.989  1254  2218 W AudioSystem: AudioPolicyService server died!
 Line 116663: 04-19 10:37:21.989  2371  2381 W AudioSystem: AudioPolicyService server died!
 Line 116664: 04-19 10:37:21.989  1452  1903 W AudioSystem: AudioPolicyService server died!
 Line 116665: 04-19 10:37:21.989   799   809 W AudioSystem: AudioPolicyService server died!
 Line 116666: 04-19 10:37:21.989   602   910 W AudioSystem: AudioPolicyService server died!
 Line 116667: 04-19 10:37:21.990  7347  7358 W AudioSystem: AudioFlinger server died!
 Line 116668: 04-19 10:37:21.990   987  3796 W AudioSystem: AudioFlinger server died!
 Line 116669: 04-19 10:37:21.990   924  1384 W AudioSystem: AudioFlinger server died!
 Line 116670: 04-19 10:37:21.990  7347  7357 W IMediaDeathNotifier: media server died
 Line 116671: 04-19 10:37:21.991   924  1100 W IMediaDeathNotifier: media server died
 Line 116672: 04-19 10:37:21.991   987  1000 W IMediaDeathNotifier: media server died
 Line 116673: 04-19 10:37:21.991   799  1304 W IMediaDeathNotifier: media server died
 Line 116674: 04-19 10:37:21.991  1254  1268 W IMediaDeathNotifier: media server died
 Line 116675: 04-19 10:37:21.991   602   617 W IMediaDeathNotifier: media server died
 Line 116678: 04-19 10:37:22.000   799   810 W AudioSystem: AudioFlinger server died!
 Line 116679: 04-19 10:37:22.001  1254  1266 W AudioEffect: IEffect died
 Line 116680: 04-19 10:37:22.001  1452  1466 W AudioSystem: AudioFlinger server died!
 Line 116681: 04-19 10:37:22.001   602   798 D AudioService:  Enter AudioSystem.AUDIO_STATUS_SERVER_DIED callback:true
 Line 116682: 04-19 10:37:22.001  1254  4499 W AudioSystem: AudioFlinger server died!
 Line 116684: 04-19 10:37:22.003  1254  1268 W MediaMetadataRetriever: MediaMetadataRetriever server died!
 Line 116686: 04-19 10:37:22.003  1254  1254 D MultiPlayer: Error: MediaPlayer.MEDIA_ERROR_SERVER_DIED
 Line 116697: 04-19 10:37:22.013  1162  5637 W MediaMetadataRetriever: MediaMetadataRetriever server died!
 Line 116724: 04-19 10:37:22.174   602   798 W AudioSystem: AudioFlinger server died!
 Line 117252: 04-19 10:37:22.563   602   948 I ActivityManager: appDiedLocked dying app : com.mediatek.mtklogger (pid 5010) has died.
 Line 117252: 04-19 10:37:22.563   602   948 I ActivityManager: appDiedLocked dying app : com.mediatek.mtklogger (pid 5010) has died.
 Line 120106: 04-19 10:37:23.674   602   722 E AudioService: Media server died.

原因一：发生段错误SIGSEGV(SEGV_MAPERR非法内存访问错误), system_server中的许多重要服务died掉，导致系统重启

 Line 1082209: 04-29 21:56:36.517 W/IMediaDeathNotifier(11111): media server died
 Line 1082211: 04-29 21:56:36.517 W/IMediaDeathNotifier(  655): media server died
 Line 1082212: 04-29 21:56:36.517 W/IMediaDeathNotifier( 2965): media server died
 Line 1082213: 04-29 21:56:36.517 W/AudioSystem(  655): AudioPolicyService server died!
 Line 1082214: 04-29 21:56:36.517 W/IMediaDeathNotifier( 2979): media server died
 Line 1082215: 04-29 21:56:36.517 W/IMediaDeathNotifier( 2771): media server died
 Line 1082216: 04-29 21:56:36.517 W/IMediaDeathNotifier(  857): media server died
 Line 1082217: 04-29 21:56:36.517 W/IMediaDeathNotifier( 1641): media server died
 Line 1082219: 04-29 21:56:36.517 W/GestureDevice( 1079): GestureDevice server died!
 Line 1082220: 04-29 21:56:36.517 I/ServiceManager(  241): service 'media.player' died
 Line 1082221: 04-29 21:56:36.517 I/ServiceManager(  241): service 'media.camera' died
 Line 1082222: 04-29 21:56:36.517 I/ServiceManager(  241): service 'media.audio_policy' died
 Line 1082223: 04-29 21:56:36.517 I/ServiceManager(  241): service 'media.audio_flinger' died
 Line 1082224: 04-29 21:56:36.517 I/ServiceManager(  241): service 'media.gestures' died
 Line 1082225: 04-29 21:56:36.517 W/MediaMetadataRetriever( 1593): MediaMetadataRetriever server died!
 Line 1082226: 04-29 21:56:36.517 W/AudioSystem( 2771): AudioPolicyService server died!
 Line 1082227: 04-29 21:56:36.517 W/AudioSystem(  655): AudioFlinger server died!
 Line 1082230: 04-29 21:56:36.527 D/MultiPlayer( 1641): Error: MediaPlayer.MEDIA_ERROR_SERVER_DIED
 Line 1082233: 04-29 21:56:36.527 W/AudioSystem(  857): AudioPolicyService server died!
 Line 1082245: 04-29 21:56:36.547 W/AudioSystem(11111): AudioFlinger server died!
 Line 1082246: 04-29 21:56:36.547 W/AudioSystem( 2771): AudioFlinger server died!
 Line 1082247: 04-29 21:56:36.547 W/AudioSystem(  989): AudioFlinger server died!
 Line 1082248: 04-29 21:56:36.547 W/AudioSystem( 1641): AudioFlinger server died!
 Line 1082249: 04-29 21:56:36.547 W/AudioSystem(  857): AudioFlinger server died!
 Line 1082250: 04-29 21:56:36.547 W/AudioEffect( 1641): IEffect died
 Line 1082251: 04-29 21:56:36.547 W/AudioSystem(  964): AudioFlinger server died!
 Line 1082754: 04-29 21:56:38.128 W/Sensors (  997): sensorservice died [0x733b5850]
 Line 1082755: 04-29 21:56:38.128 W/Sensors (  989): sensorservice died [0x72dc7590]
 Line 1082756: 04-29 21:56:38.128 W/Sensors ( 1641): sensorservice died [0x72d3e440]
 Line 1082757: 04-29 21:56:38.128 I/Atfwd_Sendcmd(  275): AtCmdFwd : binderDied
 Line 1082801: 04-29 21:56:38.148 I/ServiceManager(  241): service 'cneservice' died
 Line 1082802: 04-29 21:56:38.148 I/ServiceManager(  241): service 'connectivity' died
 Line 1082803: 04-29 21:56:38.148 I/ServiceManager(  241): service 'usb' died
 Line 1082804: 04-29 21:56:38.148 I/ServiceManager(  241): service 'serial' died
 Line 1082805: 04-29 21:56:38.148 I/ServiceManager(  241): service 'uimode' died
 Line 1082806: 04-29 21:56:38.148 I/ServiceManager(  241): service 'vivo_prox_cali_service' died
 Line 1082807: 04-29 21:56:38.148 I/ServiceManager(  241): service 'audio' died
 Line 1082808: 04-29 21:56:38.148 I/ServiceManager(  241): service 'servicediscovery' died
 Line 1082809: 04-29 21:56:38.148 I/ServiceManager(  241): service 'throttle' died
 Line 1082810: 04-29 21:56:38.148 I/ServiceManager(  241): service 'updatelock' died
 Line 1082811: 04-29 21:56:38.148 I/ServiceManager(  241): service 'notification' died
 Line 1082812: 04-29 21:56:38.148 I/ServiceManager(  241): service 'devicestoragemonitor' died
 Line 1082813: 04-29 21:56:38.148 I/ServiceManager(  241): service 'location' died
 Line 1082814: 04-29 21:56:38.148 I/ServiceManager(  241): service 'country_detector' died
 Line 1082815: 04-29 21:56:38.148 I/ServiceManager(  241): service 'search' died
 Line 1082816: 04-29 21:56:38.148 I/ServiceManager(  241): service 'dropbox' died
 Line 1082817: 04-29 21:56:38.148 I/ServiceManager(  241): service 'backup' died
 Line 1082818: 04-29 21:56:38.148 I/ServiceManager(  241): service 'appwidget' died
 Line 1082819: 04-29 21:56:38.148 I/ServiceManager(  241): service 'diskstats' died
 Line 1082820: 04-29 21:56:38.148 I/ServiceManager(  241): service 'AtCmdFwd' died
 Line 1082821: 04-29 21:56:38.148 I/ServiceManager(  241): service 'samplingprofiler' died
 Line 1082822: 04-29 21:56:38.148 I/ServiceManager(  241): service 'commontime_management' died
 Line 1082823: 04-29 21:56:38.148 I/ServiceManager(  241): service 'bbk_touch_screen_service' died
 Line 1082824: 04-29 21:56:38.148 I/ServiceManager(  241): service 'dreams' died
 Line 1082825: 04-29 21:56:38.148 I/ServiceManager(  241): service 'entropy' died
 Line 1082826: 04-29 21:56:38.148 I/ServiceManager(  241): service 'content' died
 Line 1082827: 04-29 21:56:38.148 I/ServiceManager(  241): service 'batteryinfo' died
 Line 1082828: 04-29 21:56:38.148 I/ServiceManager(  241): service 'cpuinfo' died
 Line 1082829: 04-29 21:56:38.148 I/ServiceManager(  241): service 'bluetooth_a2dp' died
 Line 1082830: 04-29 21:56:38.148 I/ServiceManager(  241): service 'bluetooth_manager' died
 Line 1082831: 04-29 21:56:38.148 I/ServiceManager(  241): service 'bluetooth' died
 Line 1082832: 04-29 21:56:38.148 I/ServiceManager(  241): service 'account' died
 Line 1082833: 04-29 21:56:38.148 I/ServiceManager(  241): service 'meminfo' died
 Line 1082834: 04-29 21:56:38.148 I/ServiceManager(  241): service 'clipboard' died
 Line 1082835: 04-29 21:56:38.148 I/ServiceManager(  241): service 'lock_settings' died
 Line 1082836: 04-29 21:56:38.148 I/ServiceManager(  241): service 'wallpaper' died
 Line 1082837: 04-29 21:56:38.148 I/ServiceManager(  241): service 'network_management' died
 Line 1082838: 04-29 21:56:38.148 I/ServiceManager(  241): service 'sensorservice' died
 Line 1082839: 04-29 21:56:38.148 I/ServiceManager(  241): service 'scheduling_policy' died
 Line 1082840: 04-29 21:56:38.148 I/ServiceManager(  241): service 'telephony.registry' died
 Line 1082841: 04-29 21:56:38.148 I/ServiceManager(  241): service 'textservices' died
 Line 1082842: 04-29 21:56:38.148 I/ServiceManager(  241): service 'netpolicy' died
 Line 1082843: 04-29 21:56:38.148 I/ServiceManager(  241): service 'hardware' died
 Line 1082844: 04-29 21:56:38.148 I/ServiceManager(  241): service 'permission' died
 Line 1082845: 04-29 21:56:38.148 I/ServiceManager(  241): service 'dbinfo' died
 Line 1082846: 04-29 21:56:38.148 I/ServiceManager(  241): service 'package' died
 Line 1082847: 04-29 21:56:38.148 I/ServiceManager(  241): service 'netstats' died
 Line 1082848: 04-29 21:56:38.148 I/ServiceManager(  241): service 'display' died
 Line 1082849: 04-29 21:56:38.148 I/ServiceManager(  241): service 'alarm' died
 Line 1082850: 04-29 21:56:38.148 I/ServiceManager(  241): service 'vibrator' died
 Line 1082851: 04-29 21:56:38.148 I/ServiceManager(  241): service 'battery' died
 Line 1082852: 04-29 21:56:38.148 I/ServiceManager(  241): service 'usagestats' died
 Line 1082853: 04-29 21:56:38.148 I/ServiceManager(  241): service 'wifi' died
 Line 1082854: 04-29 21:56:38.148 I/ServiceManager(  241): service 'gfxinfo' died
 Line 1082855: 04-29 21:56:38.148 I/ServiceManager(  241): service 'statusbar' died
 Line 1082856: 04-29 21:56:38.148 I/ServiceManager(  241): service 'activity' died
 Line 1082857: 04-29 21:56:38.148 I/ServiceManager(  241): service 'wifip2p' died
 Line 1082858: 04-29 21:56:38.148 I/ServiceManager(  241): service 'power' died
 Line 1082859: 04-29 21:56:38.148 I/ServiceManager(  241): service 'window' died
 Line 1082860: 04-29 21:56:38.148 I/ServiceManager(  241): service 'input' died
 Line 1082861: 04-29 21:56:38.148 I/ServiceManager(  241): service 'device_policy' died
 Line 1082862: 04-29 21:56:38.148 I/ServiceManager(  241): service 'mount' died
 Line 1082863: 04-29 21:56:38.148 I/ServiceManager(  241): service 'input_method' died
 Line 1082864: 04-29 21:56:38.148 I/ServiceManager(  241): service 'accessibility' died
 Line 1082865: 04-29 21:56:38.148 I/ServiceManager(  241): service 'user' died
 Line 1082866: 04-29 21:56:38.148 I/ServiceManager(  241): service 'vivo_log_service' died
 Line 1082867: 04-29 21:56:38.148 W/Sensors ( 1079): sensorservice died [0x745d5d30]
 Line 1082877: 04-29 21:56:38.148 W/AudioFlinger(11880): power manager service died !!!
 Line 1083047: 04-29 21:56:39.890 I/ServiceManager(  241): service 'media.camera' died
 Line 1083048: 04-29 21:56:39.890 I/ServiceManager(  241): service 'media.audio_policy' died
 Line 1083049: 04-29 21:56:39.890 I/ServiceManager(  241): service 'media.audio_flinger' died
 Line 1083050: 04-29 21:56:39.890 I/ServiceManager(  241): service 'media.player' died
 Line 1083051: 04-29 21:56:39.890 I/ServiceManager(  241): service 'media.gestures' died
 Line 1083057: 04-29 21:56:39.950 I/ServiceManager(  241): service 'MotionStartManager' died
 Line 1083061: 04-29 21:56:39.980 I/ServiceManager(  241): service 'simphonebook' died
 Line 1083062: 04-29 21:56:39.980 I/ServiceManager(  241): service 'phone' died
 Line 1083063: 04-29 21:56:39.980 I/ServiceManager(  241): service 'isms' died
 Line 1083064: 04-29 21:56:39.980 I/ServiceManager(  241): service 'iphonesubinfo' died
 Line 1083065: 04-29 21:56:39.980 I/ServiceManager(  241): service 'sip' died
 Line 1083122: 04-29 21:56:40.120 I/ServiceManager(  241): service 'nfc' died

syh63053767
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
计算机重启原因大概总结
11-07
1．机箱电源功率不足、直流输出不纯、动态反应迟钝。 用户或装机商往往不重视电源，采用价格便宜的电源，因此是引起系统自动重启的最大嫌疑之一。 ①电源输出功率不足，当运行大型的3D游戏等占用CPU资源较大的软件时，CPU需要大功率供电时，电源功率不够而超载引起电源保护，停止输出。电源停止输出后，负载减轻，此时电源再次启动。由于保护/恢复的时间很短，所以给我们的表现就是主机自动重启。
总结Centos7系统加固知识点
01-10
注意：此教程的云服务器以centos7以上为例，云服务器于阿里云购买 其他服务商的云服务器配置大同小异 建议：linux的服务器不建议安装图形化工具，因为占内存，占带宽，占资源，弊远大于利 手动更新系统： yum -y update 防火墙配置： service firewalld start //启动防火墙 systemctl enable firewalld.service //开机自启 selinux配置： vim /etc/selinux/config 修改： SELINUX=enforcing //设置强制模式 reboot //重启生效 ssh配置：（防暴力破解）
Linux系统常用指令总结
01-07
来源 | CSDN 博客 作者 | 不撸代码闲得慌，责编 | Carol 出品 | CSDN云计算（ID：CSDNcloud） 系统的运行级别 0：关机 1：单用户模式（可以找回丢失的密码） 2：多用户状态没有网络服务 3：多用户状态有网络服务 4：系统未使用保留给用户 5：图形界面 6：系统重启 注意：在/etc/inittab文件中可以修改默认的运行级别 切换到指定的运行级别 默认指令 帮助指令 1：获取帮助信息 2：help指令 文件目录类指令 1：pwd 查看当前工作目录的绝对路径 2：ls指令 3：cd指令 4：mkdir指令（用于创建目录的指令） 5：rmdir
Android的BUG - 广为人知的诟病：频繁重启问题
mmdev
06-26 423
使用过Android的同学，尤其是用过山寨pad，应该对Android的重启问题印象深刻吧。Android由于其设计的复杂性，可能会使得系统在不经意时陷入异常状态，因此Android设计了一套看门狗机制，当检测到问题后，自动重启。 再说说我碰到的问题吧，刚带起Android的时候，android的重启问题异常严重，经常操作一会后，界面卡住，等待1分钟左右，重启…， trace大约如下： W/W...
系统卡死问题分析
b178903294的博客
04-03 4952
问题背景： 测试对平板 系统进行monkey压测时，出现了应用界面卡死的情况。 测试脚本：monkey --ignore-crashes --ignore-timeouts --kill-process-after-error --ignore-security-exceptions --throttle 200 -v -v -v -s 5 10000000 1>>/sdcard/log.log 2>>/sdcard/log_err.log 一边测试一边抓取logcat并.
SensorService启动
许浑的博客
08-01 2270
SensorService启动 SystemServer进程启动SensorService 系统启动system_server进程，SystemServer.java 负责启动 startSensorService() frameworks/base/services/java/com/android/server/SystemServer.java system_server进程启动 new SystemServer().run() private void run() { /
无法录音原因总结
syh63053767的专栏
05-04 2万+
原因七：MIC硬件坏掉，导致无法录音 原因六：找不到编码库的时候，MediaRecord：error(1,,-2147483648), 05-07 22:23:18.924 E/OMXCodec(  251): ---hd%--- componentName=OMX.google.aac.decoder, matchComponentName=(null), index=20, matchIn
Android5.0L中SensorService crash导致的systemserver重启问题分析
宋金时的专栏
07-03 4925
一、初步分析结论sensorservice多线程机制存在问题，导致在disable accel sensor并释放相应内存和数据之后，有很小的概率发生继续读取到未处理完的sensor事件，从而继续使用相应的内存和数据，并且没有做相应的防御保护措施，最终引起指针地址操作错误。二、解决方案1、首先在可能发生错误的地方做好防御保护措施2、对多线程进行同步，对于临界变量的操作都放置到临界区中，使用锁来保护
视频文件直接放在服务器里播放卡,在内部存储上播放视频时弹出SD卡导致“媒体服务器死机”...
weixin_29130255的博客
08-01 551
我正在为硬件设备开发android应用程序和固件，该设备在/ mnt / sdcard上有内部存储 . 插入外部SD卡时，它安装在/ mnt / sdcard / extsd，/ mnt / sdcard / udisk安装在外部USB盘(拇指驱动器)上 .现在的问题是，当我使用“VideoView”在内部存储上播放视频并弹出外部SD卡时，会弹出一个“抱歉，无法播放视频”的弹出窗口 .我看了一下l...
Android 4.0 framework源码修改编译，模拟器运行不起来——解决
liujianminghero的专栏
09-06 3510
最近在看frameworks里的源码，手痒了，便想改改看看效果，没想到改完后，模拟器却运行不起来了。         首先声明，我是用的android 4.0.3 ICS的源码，编译好后，利用编译好的镜像启动的模拟器，以前修改过里面的Launcher，将生成的Launcher.apk和Launcher.odex  push后是成功的。 现在我在 frameworks/base/polic
Android系统重启问题的归类
11-05
当Android发生系统重启，即导致kernel重启的异常时，会在手机中的/data/aee_exp目录下保存异常重启的db。工程师可以通过GAT的bug report功能，或者直接通过adb pull，把对应的db从手机中抓回来。
Linux 系统日常使用总结
01-09
目录基本操作bash界面输入命令帮助命令关机重启标准文件架构文件操作set $PATH variable软件安装卸载Dpkg命令apt命令卸载软件软件源程序无响应 结束进程rar的解压出错 基本操作 bash界面 【nbcc@localhost～】$ ...
【Android 系统开发】CyanogenMod 13.0 源码下载 编译 ROM 制作 ( 手机平台 : 小米4 | 编译平台 : Ubuntu 14.04 LTS 虚拟机)
热门推荐
让 学习 成为一种 习惯 ( 韩曙亮 の 技术博客 )
06-15 3万+
CyanogenMod 13.0 编译
android移植（三）-一些问题与解决方法
zmlovelx(帅得不敢出门 程序员群31843264)
04-18 4395
板子helper2416    芯片是三星的s3c2416  arm平台   本机系统： opensuse ============================================================================== 命令行让Android播放音乐 插tf卡开机之后，运行 gdb shell am start -n com.android
Android启动错误“Waiting for sevice media.audio_flinger”的解决方案(全）
kulolun的专栏
01-23 3839
今天发现我们的android系统安装了国外的一个电子市场后，这个APK无法运行，发现是“Waiting for sevice media.audio_flinger”。 系统启动时没有启动medaisever服务 具体为init.rc中的 service media /system/bin/mediaserver    user media     group
解决rk3288启动SurfaceFlinger 初始化失败问题
lb5761311的专栏
06-13 6741
最近编译rk3288源码遇到一个奇怪的问题，正常编译使用的Android源码。如果做一些改动之后。再烧录启动失败很是苦恼，主要报下面错误 kernel 失败日志 [ 4.088148] EXT4-fs (mmcblk0p12): recovery complete [ 4.088569] EXT4-fs (mmcblk0p12): mounted filesystem with o...
查看动态库so命令
syh63053767的专栏
11-04 1万+
adb logcat -s AndroidRuntime  adb shell nm -D /system/lib/libqcomfm_jni | grep "android_hardware_fmradio_FmReceiverJNI_acquireFdNative" adb shell nm -D /system/lib/libqcomfm_jni.so  adb pull /syste
Linux操作系统及应用的samba给我一个实验总结
最新发布
05-25
Samba是一个开源的实现SMB/CIFS协议的软件，可以在Linux系统上实现与Windows系统的文件共享和打印机共享等功能。下面是一个简单的实验总结： 实验环境： - 一台安装了Linux操作系统的电脑 - 一台安装了Windows操作系统的电脑 实验步骤： 1. 在Linux系统上安装samba。可以使用以下命令安装： ``` sudo apt-get install samba ``` 2. 创建一个共享文件夹。可以使用以下命令创建一个名为“share”的文件夹并设置共享权限： ``` sudo mkdir /home/share sudo chmod 777 /home/share ``` 3. 配置samba服务。可以编辑/etc/samba/smb.conf文件来配置samba服务。在文件末尾添加以下内容： ``` [share] comment = Shared Folder path = /home/share browseable = yes writable = yes guest ok = yes read only = no ``` 4. 重启samba服务。可以使用以下命令重启samba服务： ``` sudo service smbd restart ``` 5. 在Windows系统上连接共享文件夹。可以使用以下步骤连接： - 打开“文件资源管理器”，在地址栏输入“\ \ Linux主机名”，例如“\ \ ubuntu”。 - 输入Linux系统的用户名和密码，连接到共享文件夹。 6. 在Windows系统上访问共享文件夹。可以在Windows系统上打开共享文件夹，创建、编辑和删除文件。 总结： 通过以上实验，我们可以学习到如何在Linux系统上安装和配置samba服务，以及如何在Windows系统上连接和访问共享文件夹。这对于在Linux和Windows系统之间的文件共享和协作非常有用。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值